Skip to main content
Every request to the Partna API must include two headers: x-api-key and x-api-user.

​
Headers

HeaderDescription
x-api-keyYour API key. Provided during onboarding for both staging and production.
x-api-userYour merchant username. Provided during onboarding.

​
Example request

curl --request GET \
  --url https://staging-api.getpartna.com/v4/rate \
  --header 'x-api-key: sk_staging_abc123...' \
  --header 'x-api-user: your-merchant-username'

​
Managing API keys

You can generate, rotate, and revoke API keys programmatically:
ActionEndpoint
Generate a new keyPOST /user/api-key
List all keysGET /user/api-keys
View key scopesGET /user/api-key/scopes
Invalidate a keyPOST /user/api-key/invalidate
Delete a keyDELETE /user/api-key

​
Security best practices

Never expose your API key in client-side code. All API calls should be made from your backend server. The x-api-key grants full access to your merchant account. Use separate keys for staging and production. Your staging credentials only work against the staging environment and vice versa. Rotate keys periodically. Use the Generate API Key endpoint to create a new key, update your integration, then invalidate the old key.

​
Getting credentials

If you do not have credentials yet, request access here. The Partna team will contact you to complete onboarding and set up your merchant account. Once your account is active, generate your API keys from the dashboard: