Headers
All Elite Neo Bank API requests must include the required authentication headers to securely communicate with the Elite Neo Bank infrastructure. These headers are used to:- Identify your merchant account
- Validate request authenticity
- Verify payload integrity
- Prevent replay attacks
- Secure API communication
- API Key
- Timestamp
- HMAC SHA256 Signature
Required Headers
Header Reference
X-API-KEY
TheX-API-KEY uniquely identifies your merchant account within the Elite Neo Bank platform.
This key is provided during merchant onboarding and is required for all API requests.
Example
Important Notes
- Sandbox and production API keys are different
- Invalid API keys may result in:
- Never expose production API keys publicly
X-TIMESTAMP
TheX-TIMESTAMP header contains the current UNIX timestamp in seconds.
Elite Neo Bank validates timestamps to:
- Prevent replay attacks
- Verify request freshness
- Improve API security
Example
Important Notes
- Timestamp must be generated dynamically
- Use UNIX seconds format only
- Expired timestamps may be rejected
- Server time should remain synchronized
X-SIGNATURE
TheX-SIGNATURE header contains the HMAC SHA256 generated request signature.
This signature verifies:
- Merchant authenticity
- Request integrity
- Payload validity
➡️ Authentication → Signature
Example
Important Notes
- Signatures must always be generated server-side
- Never expose your secret key publicly
- Payload modifications after signing will invalidate the request
- Invalid signatures may result in:
Content-Type
Elite Neo Bank APIs accept JSON request payloads only.Required Value
Accept Header
TheAccept header specifies the expected API response format.
Required Value
Example Request
Common Authentication Errors
401 Unauthorized
Possible reasons:- Invalid API key
- Incorrect signature
- Expired timestamp
- Missing authentication headers
400 Bad Request
Possible reasons:- Invalid JSON payload
- Missing required fields
- Incorrect request structure
Security Recommendations
- Always generate signatures server-side
- Never expose secret keys publicly
- Use HTTPS only
- Generate fresh timestamps for every request
- Validate webhook signatures before processing callbacks
