API Key
Your API key is the foundation of all authentication. It grants unlimited, repeatable access and is used for most API calls. Pass it using either header format:Session Token
A Session Token is generated from your API key via an API call. It is valid for 5 minutes and can be used for any API call during that time. Generate a session token:Access Token
An Access Token is generated locally using your API key and PCI Booking’s SSL certificate. Unlike the session token, no API call is needed to create it. You choose its expiration time: any moment in the future, at most 24 hours ahead. It is single-use only.How it works
- Download PCI Booking’s SSL certificate from
https://service.pcibooking.net/api - Run the generation script locally (see code samples below)
- The script builds a data block in the format
<APIKey>#<GUID>#<ExpirationTime>and encrypts it with the certificate’s public key - The output is your access token
Pass it as a query parameter:
Code Samples
The samples below cap the expiration at 1 hour as a conservative best practice - the API itself accepts any expiration up to 24 hours ahead.
- C#
- Java
- PHP
- Python
Comparison
Which should I use?
- Server-to-server calls (processing payments, managing tokens, configuring settings): use the API key
- Browser-facing operations (card entry form iframe, card display): use a Session Token or Access Token. Your API key must never be exposed to the browser.
- Need precise control over expiry and single-use guarantees: use an Access Token
- Quick integration for browser operations: use a Session Token (simpler, just one API call)
Related
- Create an Account - Get your API keys and portal access
- Quickstart - End-to-end integration walkthrough
- Testing and Going Live - Move from sandbox to production
- API Conventions - Request formats, headers, and common patterns

