Skip to main content
POST
/
v1
/
entries
curl --request POST \
  --url https://plugin-br-pix-direct-jd.sandbox.lerian.net/v1/entries \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "key": "+5511987654321",
  "keyType": 3,
  "accountId": "01989f9e-6508-79f8-9540-835be49fbd0d",
  "isValidated": false
}'
{
  "key": "+5511987654321",
  "keyType": 3,
  "keyTypeDescription": "keyType 3 = PHONE",
  "status": 0,
  "statusDescription": "FINALIZED",
  "statusComment": "status 0 = FINALIZED/pending confirmation"
}

Authorizations

​
Authorization
string
header
required

JWT Bearer token authentication. Obtain token from /v1/login/oauth/access_token endpoint using client credentials (clientId and clientSecret).

Include token in Authorization header: Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...

Token expires after 3600 seconds (1 hour).

Body

application/json
​
keyType
enum<integer>
required

Pix key type identifier. Numeric codes that specify the type of Pix key being used.

Valid values:

  • 0 = CPF (Individual taxpayer ID with 11 digits, e.g., "12345678901")
  • 1 = CNPJ (Company taxpayer ID with 14 digits, e.g., "12345678000190")
  • 2 = EMAIL (Email address, e.g., "user@example.com")
  • 3 = PHONE (Phone number in international format, e.g., "+5511987654321")
  • 4 = EVP (Random UUID key automatically generated, e.g., "123e4567-e89b-12d3-a456-426614174000")
Available options:
0,
1,
2,
3,
4
Example:

3

​
accountId
string<uuid>
required

Account identifier.

Example:

"01989f9e-6508-79f8-9540-835be49fbd0d"

​
isValidated
boolean
required

Indicates if the key has been pre-validated (e.g., email/phone verified).

Example:

false

​
key
string

Pix key value (optional for EVP/random keys which are auto-generated). Format depends on keyType: CPF (11 digits), CNPJ (14 digits), Email (valid email), Phone (+55 prefix), or omit for EVP.

Example:

"+5511987654321"

Response

Pix key created successfully

​
key
string
required

Pix key value.

Example:

"+5511987654321"

​
keyType
enum<integer>
required

Pix key type identifier. Numeric codes that specify the type of Pix key being used.

Valid values:

  • 0 = CPF (Individual taxpayer ID with 11 digits, e.g., "12345678901")
  • 1 = CNPJ (Company taxpayer ID with 14 digits, e.g., "12345678000190")
  • 2 = EMAIL (Email address, e.g., "user@example.com")
  • 3 = PHONE (Phone number in international format, e.g., "+5511987654321")
  • 4 = EVP (Random UUID key automatically generated, e.g., "123e4567-e89b-12d3-a456-426614174000")
Available options:
0,
1,
2,
3,
4
Example:

3

​
status
enum<integer>
required

Pix key registration status code. Indicates the current state of a Pix key in its lifecycle.

Valid values:

  • -1 = CANCELLED (Key registration was cancelled)
  • 0 = FINALIZED (Key is finalized/pending confirmation)
  • 1 = ACTIVE (Key is active and operational)
  • 2 = WAITING_OWNERSHIP_CONFIRMATION (Awaiting ownership confirmation from the user)
  • 3 = CREATING (Key is being created in the system)
  • 4 = IM_CLAIMER_PENDING_CONFIRM_CLAIM_REQUEST (I am claimer, pending claim confirmation)
  • 5 = IM_CLAIMER_PENDING_OWNER_GIVEWAY (I am claimer, awaiting current owner to release the key)
  • 6 = IM_OWNER_PENDING_GIVEAWAY_CONFIRM (I am owner, pending approval to transfer key)
  • 7 = IM_CLAIMER_AND_OWNER_GAVEAWAY_PENDING_MY_CONFIRM (Transfer initiated, awaiting my confirmation)
Available options:
-1,
0,
1,
2,
3,
4,
5,
6,
7
Example:

1

​
statusDescription
string
required

Human-readable status description corresponding to the numeric status code.

Example:

"PENDING_CONFIRMATION"