Activate Virtual Accounts
The virtual account creation is a 2-step process (using the reservation and activation services), you can use POST and PUT endpoints one after another.
Use PUT verb for Activation action
- The API support XML and JSON formats.
- The reservation/activation functionality is identified based on the request payload (action).
- You specify values for input parameters in the body of your XML/JSON document.
- You encrypt the payload, place it in your request and send it with your application.
<font size=‘2’>Content-Type: Supports application/xml and application/json.
Authorization: The OAuth Token prefixed with Bearer and space in between.
Allowed characters: A-Z, a-z, 0-9, Space
Allowed punctuation marks: ’ ( ) * - , . / : ; _ & $ # @ [ ]
Authentication
All CitiConnect APIs use the oAuth2 authentication scheme, which requires a bearer token to authenticate your API call. The Token URL includes the version of authentication used by this API. See the Citi Authentication API reference for information on requesting a token.
Query parameters
Unique reference shared during CitiConnect API onboarding (client_id used during OAuth token generation).
Request
Action is a request type.
- Choose the action value as ”ACTIVATION”, if you want to activate the virtual account which was reserved earlier.
Response headers
The date when this API was stopped or will be stopped by the system owner. ISO 8601-1:2019 format.
The date when this API will no longer be Supported by the system owner. The API will no longer be responsive and all REQUESTS will generate an error. ISO 8601-1:2019 format.
The remaining window before the rate limit resets. ISO 8601-1:2019.
Response
Auto-generated unique identification assigned for the request.
Status of the request.
Possible statuses are
SUCCESS
REJECTED
PENDING
Action of the given request.
- ”RESERVATION”
- ”ACTIVATION”.