Create an API credential
Creates an API credential for the company account identified in the path. In the request, you can specify the roles and allowed origins for the new API credential.
The response includes the:
- API key: used for API request authentication.
- Client key: public key used for client-side authentication.
- Username and password: used for basic authentication.
Make sure you store the API key securely in your system. You won't be able to retrieve it later.
If your API key is lost or compromised, you need to generate a new API key.
To make this request, your API credential must have the following roles:
- Management API—API credentials read and write
The unique identifier of the merchant account.
The list of allowed origins for the new API credential.
Description of the API credential.
List of roles for the API credential. Only roles assigned to 'ws@Company.<CompanyName>' can be assigned to other API credentials.
After submitting a call, you receive a response message to inform you that your request was received and processed.
Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.
HTTP Responses
200 - OK
The request has succeeded.
204 - No Content
The request has been successfully processed, but there is no additional content.
400 - Bad Request
A problem reading or understanding the request.
401 - Unauthorized
Authentication required.
403 - Forbidden
Insufficient permissions to process the request.
422 - Unprocessable Entity
A request validation error.
500 - Internal Server Error
The server could not process the request.