Skip to main content
All partner HTTP APIs authenticate with an API key header.

​
Partner API key

Send your portal consumer key as:
Used by /v1, /v2, /account, /{currency}, and /utility.

​
Checkout key

Checkout endpoints under /v1/checkout use your portal checkout key in the same header:
Do not use the consumer key on checkout routes (and vice versa).

​
AI agents (MCP)

Cursor, Claude, and ChatGPT do not call these headers directly. Configure the Pretium MCP server; it uses your partner API key (and secret key for register_agent) on your behalf.

​
Request headers

​
IP allowlisting

You can register allowed IPs in the partner portal. Prefer allowing only your production egress IPs.

​
Keys in the portal

From the merchant portal you can:
  • View / rotate the consumer key
  • View the checkout key
  • View the secret key (for MCP register_agent)
  • Configure webhook URLs and IP allowlists