Authorization
Authenticate JGME Pay API requests using client-id and client-secret headers.
Every JGME Pay API request is authenticated using two headers:
client-idclient-secret
Never expose client-secret in frontend apps, mobile apps, browser storage,
or public repositories.
Authentication Model
client-id
Public identifier for your account and environment.
client-secret
Secret key used to authorize requests. Store only on trusted backend systems.
Header-Based Auth
Pass both credentials in request headers on every API call.
Keep Keys Server-Side
Your credentials authorise live transactions. Never ship them to a browser or mobile client.
Where To Get Your Keys
Sign in to Dashboard
Open API key settings
Navigate to Settings -> Security -> API Keys and Webhooks.
Copy credentials securely
Save your client-id and client-secret into server environment variables.
Request Example
curl --location 'https://api.jgmepay.com/payments/v1/checkouts' \
--header 'client-id: <your-client-id>' \
--header 'client-secret: <your-client-secret>' \
--header 'Content-Type: application/json' \
--data '{
"reference": "test-001",
"amount": 1000,
"currency": "NGN",
"country": "NG",
"user": {
"phoneNumber": "08012345678"
}
}'Common Mistakes
Frontend code is public to end users. Keep all authenticated JGME Pay API calls on your backend.
Requests without either client-id or client-secret will fail
authentication.
Always load credentials from environment variables or a secure secret manager.
Security Checklist
- Keep
client-secreton backend only. - Use HTTPS for API and webhook endpoints.
- Rotate credentials if exposure is suspected.
- Restrict internal access to production secrets.