Returns the API credential identified in the path.
To make this request, your API credential must have the following roles:
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.
The request has succeeded.
Show more Show lessReferences to resources linked to the API credential.
Company account that the API credential is linked to. Only present for company-level webhooks.
Generates a new API key. When you generate a new one, the existing key remains valid for 24 hours.
Generates a new client key, used to authenticate client-side requests. When you generate a new one, the existing key remains valid for 24 hours.
The merchant account that the API credential is linked to. Only present for merchant-level API credentials.
Indicates if the API credential is enabled. Must be set to true to use the credential in your integration.
List of IP addresses from which your client can make requests.
If the list is empty, we allow requests from any IP. If the list is not empty and we get a request from an IP which is not on the list, you get a security error.
List containing the allowed origins linked to the API credential.
References to resources linked to the allowed origin.
List of merchant accounts that the API credential has explicit access to. If the credential has access to a company, this implies access to all merchant accounts and no merchants for that company will be included.
Public key used for client-side authentication. The client key is required for Drop-in and Components integrations.
List of roles for the API credential.
The name of the API credential, for example ws@Company.TestCompany.