# Create a managed account Creates a managed account for the consumer or corporate identity. The Managed Account Profile (configured in the Multi Portal) specified determines the behavior and restrictions that the managed account will have." Endpoint: POST /managed_accounts Version: 3.63.5 Security: auth_token, api-key ## Header parameters: - `idempotency-ref` (string) A unique call reference generated by the caller that, taking into consideration the payload as well as the operation itself, helps avoid duplicate operations. Idempotency reference uniqueness is maintained for at least 24 hours. ## Request fields (application/json): - `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. - `friendlyName` (string, required) The friendly name to be given to the managed account. - `currency` (string, required) The currency expressed in ISO-4217 code. Example: GBP, EUR, USD. - `tag` (string) The tag field is a custom field that can be used to search and filter. ## Response 200 fields (application/json): - `id` (string, required) The unique identifier of a Managed Account. - `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. - `tag` (string) The tag field is a custom field that can be used to search and filter. - `friendlyName` (string, required) The friendly name given to the managed account. - `currency` (string, required) The currency expressed in ISO-4217 code. Example: GBP, EUR, USD. - `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. - `balances.availableBalance` (integer) The funds available for transactions on the instrument. Funds that are blocked or pending are not included in the available balance. - `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. - `state` (object, required) - `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" - `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" - `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" - `creationTimestamp` (integer, required) The time when the managed account was created, expressed in Epoch timestamp using millisecond precision. ## 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 409 fields (application/json): - `errorCode` (string) Enum: "PROFILE_NOT_FOUND", "PROFILE_INACTIVE", "MODEL_CONSTRAINTS_VIOLATED", "CURRENCY_NOT_SUPPORTED_BY_PROFILE", "PROVIDER_NOT_SUPPORTED_BY_PROFILE", "INSTRUMENT_NOT_FOUND", "OWNER_IDENTITY_NOT_VERIFIED", "IDENTITY_LIMITS_EXCEEDED", "PROGRAMME_LIMITS_EXCEEDED", "INNOVATOR_LIMITS_EXCEEDED", "SYSTEM_LIMITS_EXCEEDED" ## Response default fields (application/json): - `code` (string) - `message` (string) ## Response 401 fields ## Response 429 fields ## Response 500 fields ## Response 503 fields