Skip to main content
GET
List Merchant Pix Keys
Returns one row per account — the merchant identified by we_id plus every submerchant registered under it — together with the Pix key held by that account. There is no pagination: the response always covers the whole hierarchy, and the filters narrow down the rows that are returned.Accounts with no Pix key are not listed. A merchant with no eligible account still answers 200 with an empty data array and zeroed counters — never 404.

Query Parameters

integer
required
WE ID of the merchant whose hierarchy is listed. The response covers this merchant and its submerchants.Must be within the scope of the authenticated credentials, otherwise the request is rejected with 403.Example: 1020100
string
Narrows the result down to the accounts whose WE ID starts with the supplied value, so the search box of a panel filters the list while the ID is being typed.Digits only, up to 20 characters. 10201 matches 1020101; 0101 does not.Example: 1020101
string
Narrows the result down to the accounts whose company name contains the supplied value. Case and accent insensitive: jose matches JOSÉ.Up to 150 characters.Example: retail
string
Narrows the result down to the accounts whose company document contains the supplied digits. Both sides are compared digits only, so a mask is accepted: 34.881.207/0001-46, 34881207000146 and 34881 all match the same account.Up to 20 characters. A value with no digit at all is treated as no filter, instead of matching everything.Example: 34.881
string
default:"active"
Status of the Pix key. Applied by default even when omitted, so a request with no status returns the active keys.Allowed values: activeThis is currently the only accepted value — any other value is rejected with 422. Consequently, pix_key.status always comes back as ACTIVE.
Filters are combined with AND: an account is returned only when it satisfies every supplied filter.

Response

object
Counters of the listing, meant to feed a “X of Y accounts” label.
array
Accounts and their Pix keys. The queried merchant always comes first, followed by the submerchants ordered by ascending WE ID.

Errors

Because the response depends on the scope of the caller, it is never cached at the gateway. Two different credentials asking for the same we_id may legitimately receive different results.

Example request

cURL

List Account Opening Requests

Find the WE IDs of the accounts in your hierarchy

Create Company

Register a new submerchant