API Version
- Current Version: v1
- URL Format:
https://{domainName}/v1/{endpoint}
Different API versions represent distinct interfaces. Ensure you use the correct version for your integration.
Message Structure
Request Components
All API requests follow this structure:Required Headers
Digital signature in format:
algorithm=SHA256withRSA, keyVersion=1, signature=****Your assigned client identifier, used to identify your application and associated keys
ISO 8601 timestamp with minimum second accuracy (e.g.,
2024-01-10T12:00:00+01:00)application/json; charset=UTF-8Response Structure
All responses include a standardizedresult object:
Status indicator:
S- SuccessF- FailedU- UnknownA- Accepted (processing)
Error or success code (max 64 characters)
Detailed description of the result (max 256 characters)
Developer Workflow
1
Understand Requirements
Review API idempotency requirements and authentication specifications
2
Generate Keys
Create a 2048-bit RSA key pair for signing requests
3
Construct Request
Build signed, encoded requests per the message structure specification
4
Send Request
Submit HTTPS POST requests to the appropriate endpoint
5
Validate Response
Verify the response signature using the platform’s public key
6
Handle Result
Process result codes and implement appropriate error handling
Security Requirements
Request Signing
All requests must be digitally signed using RSA-SHA256
Response Validation
Always verify response signatures before processing data
Key Management
Use 2048-bit RSA keys exclusively for the SHA256withRSA algorithm
Message Encoding
Proper encoding prevents character ambiguities during transmission
Next Steps
Idempotency
Learn how to handle retries safely
Message Encoding
Understand encoding requirements
API Signing
Step-by-step signing guide
Data Dictionary
Common data types and models