Skip to main content
POST
This method lets you verify that the PCI Booking service is available and that your API key is valid.

Authentication Guide

Learn about API key authentication

Error Responses

Both POST and GET methods are supported:

Error detail

Each condition below gives the exact moreInfo text, why it happens and how to resolve it. The full set is on the Error Handling page.
HTTP status: 401message: Missing authentication headermoreInfo: one of the following, depending on which scheme the endpoint uses:
Reason. The request carried no Authorization header at all. This is a missing header, not a rejected credential - a wrong or expired credential returns -1003 instead.How to resolve.
  1. Add an Authorization header. For API key auth the value is your key prefixed with APIKEY, for example APIKEY your-api-key.
  2. Check that your HTTP client is not stripping the header on redirect. A 301 or 302 between your client and the API drops Authorization in most clients.
See also: Authentication
HTTP status: 401message: You are not authorized to access this resource. Please contact customer support.moreInfo:
The two expiration variants apply to one-time access tokens: the first means the token has passed its expiry, the second that the requested lifetime exceeded the maximum allowed and was refused outright rather than capped.Reason. Authentication itself failed: the API key or session token was not recognised, has expired, or belongs to a different environment than the endpoint you called.How to resolve.
  1. Confirm the APIKEY prefix is present and there is a single space between it and the key.
  2. Confirm the key belongs to the same environment as the host you called. Sandbox and production keys are not interchangeable.
  3. If you are using a session token, check it has not passed its time to live and start a new session if it has.
See also: Authentication

Parameters

Headers

string
required
Your API key prefixed with APIKEY. Example: APIKEY your-api-key. See the Authentication guide.

Response