# Get all managed accounts Retrieves all managed accounts belonging to the logged-in identity. Endpoint: GET /managed_accounts Version: 3.63.5 Security: auth_token, api-key ## Query parameters: - `offset` (integer) The offset value for paging, indicating the initial item number to be returned from the data set satisfying the given criteria. Leave out to fetch the first page of results. - `limit` (integer) The limit of the results for paging, starting at the offset. Limit is always capped at 100. - `profileId` (string) Filter by the managed account/card profile. Leave out to fetch all managed accounts/card. - `friendlyName` (string) Filter by the managed account/card friendly name. Leave out to fetch all managed accounts/card. The exact name must be provided, as wildcards are not supported. - `state` (array) Enum: "ACTIVE", "BLOCKED", "DESTROYED" - `state.blockedReason` (array) Enum: "USER", "SYSTEM", "LOST" - `state.destroyedReason` (array) Enum: "SYSTEM", "USER", "LOST", "STOLEN", "EXPIRED", "COMPROMISED" - `currency` (string) Filter by the managed account/card currency. Currencies are expressed as an ISO 4217 code. Leave out to fetch all managed accounts/card. - `createdFrom` (integer) Filter for managed accounts/cards created after createdFrom timestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. Leave out to fetch all managed accounts/cards. - `createdTo` (integer) Filter for managed accounts/cards created before createdTo timestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. Leave out to fetch all managed accounts/cards. - `tag` (string) Filter by the managed account/card tag. The exact tag must be provided, as wildcards are not supported. Leave out to fetch all managed accounts/card. ## Response 200 fields (application/json): - `accounts` (array) The filtered managed accounts list. - `accounts.id` (string, required) The unique identifier of a Managed Account. - `accounts.profileId` (string, required) The profile Id which a specific identity, instrument or transaction type is linked to. Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply. You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs. Profile Ids can be found in the Multi Portal, in the API Credentials page. - `accounts.tag` (string) The tag field is a custom field that can be used to search and filter. - `accounts.friendlyName` (string, required) The friendly name given to the managed account. - `accounts.currency` (string, required) The currency expressed in ISO-4217 code. Example: GBP, EUR, USD. - `accounts.balances` (object, required) Instruments with funds have 2 balances, the availableBalance indicating the funds that are available for transactions such as purchases, and the actualBalance indicating the funds that are actually on the instrument. - `accounts.balances.availableBalance` (integer) The funds available for transactions on the instrument. Funds that are blocked or pending are not included in the available balance. - `accounts.balances.actualBalance` (integer) The funds that are actually on the instrument. Funds that are blocked or pending, due to for example, a purchase authorisation or a pending deposit, are included in the actual balance. - `accounts.state` (object, required) - `accounts.state.state` (string, required) The state of the instrument indicating what it can and cannot do as follows: - ACTIVE: The instrument is in an active state and can be used in transactions. - BLOCKED: The instrument is temporarily blocked and cannot be used. Any funds on the instrument are also frozen. The blockedReason provides more information as to why it was blocked. - DESTROYED: The instrument has been permanently destroyed. The destroyReason provides more information as to why it was destroyed. Enum: "ACTIVE", "BLOCKED", "DESTROYED" - `accounts.state.blockedReason` (string) The reason why the instrument has been blocked: - USER: The root, or an authorised user, of the identity owning the instrument has temporarily blocked the instrument. - SYSTEM: The platform or an administrator of the platform has temporarily blocked the instrument. - LOST: The instrument has been blocked because it was marked as lost. Enum: "USER", "SYSTEM", "LOST" - `accounts.state.destroyedReason` (string) The reason why the instrument has been destroyed: - SYSTEM: The platform or an administrator of the platform has destroyed the instrument. - USER: The root, or an authorised user, of the identity owning the instrument has destroyed the instrument. - LOST: The instrument was automatically destroyed as it was marked as lost. - STOLEN: The instrument was automatically destroyed as it was marked as stolen. - EXPIRED: The instrument was automatically destroyed as it expired. - COMPROMISED: The instrument was automatically destroyed as it was marked as compromised. Enum: "SYSTEM", "USER", "LOST", "STOLEN", "EXPIRED", "COMPROMISED" - `accounts.creationTimestamp` (integer, required) The time when the managed account was created, expressed in Epoch timestamp using millisecond precision. - `count` (integer) The total number of records (excluding the paging limit). - `responseCount` (integer) The total number of records returned in this response (always capped at 100). ## Response 400 fields (application/json): - `message` (string) When present helps to identify and fix the problem. - `syntaxErrors` (object) Is returned as part of an HTTP error response whenever a syntax error is detected. A list of the fields together with their syntax error will be provided. - `syntaxErrors.invalidFields` (array) - `syntaxErrors.invalidFields.params` (array) - `syntaxErrors.invalidFields.fieldName` (string) - `syntaxErrors.invalidFields.error` (string) Enum: "REQUIRED", "HAS_TEXT", "REQUIRES", "SIZE", "RANGE", "IN", "NOT_IN", "REGEX", "EXACTLY", "AT_LEAST", "AT_MOST", "ALL_OR_NONE" ## Response 403 fields (application/json): - `errorCode` (string) Enum: "STEP_UP_REQUIRED", "ACCESS_TOKEN_REQUIRED" ## Response default fields (application/json): - `code` (string) - `message` (string) ## Response 401 fields ## Response 429 fields ## Response 500 fields ## Response 503 fields