Skip to main content

NetValve API Authentication

NetValve APIs authenticate with an API Key and a Client ID. Both are issued during onboarding and must be sent as HTTP headers on every server-side request.

HeaderValue
netvalve-api-keyYour API Key
netvalve-client-idYour Client ID
cURL
curl -X POST {{paymentApiUrl}}/sale \
  -H "Content-Type: application/json" \
  -H "netvalve-api-key: YOUR_API_KEY" \
  -H "netvalve-client-id: YOUR_CLIENT_ID" \
  -d '{ ... }'
Keep credentials server-side

Your API Key is a secret. Never embed it in browser or mobile code. Browser-facing integrations (Checkout SDK, Token Fields, HPP) use a short-lived session token minted by your backend instead. See the Checkout SDK guide.

Each environment has its own set of credentials. See Environments for the sandbox and production base URLs.