HMAC-SHA256 Authentication
UnicyFalcon API uses HMAC-SHA256 authentication to ensure the security and integrity of requests.Getting Your Credentials
Navigate to Settings
Log in to your UnicyFalcon dashboard and go to Settings > Applications > API Keys
Required Headers
Each request must include three authentication headers:Signature Algorithm
The signature is generated using the following algorithm:Payload Components
- METHOD: HTTP method in uppercase (GET, POST, PUT, DELETE)
- URI: Full URI path (e.g.,
/api/v1/customers) - BODY: Request body (empty string for GET requests)
- TIMESTAMP: Unix timestamp of the request
Example Implementation
Timestamp Validation
To prevent replay attacks, the timestamp must not exceed 5 minutes difference from the server time.If your timestamp is outside the allowed window, you’ll receive a
401 Unauthorized error with the message: “Request timestamp expired”Testing Your Authentication
You can test your authentication using our interactive API browser at:Common Errors
401 - Invalid or Missing API Credentials
401 - Invalid or Missing API Credentials
- Check that your API Key is correct
- Verify your HMAC Secret is accurate
- Ensure all three headers are present
401 - Request Timestamp Expired
401 - Request Timestamp Expired
- Your timestamp is more than 5 minutes old
- Sync your server time with NTP
- Regenerate timestamp for each request
401 - Invalid Signature
401 - Invalid Signature
- Verify the payload format:
METHOD|URI|BODY|TIMESTAMP - Ensure URI includes
/api/v1/prefix - Check that body is exact JSON string (no formatting)
- Confirm you’re using HMAC-SHA256 with binary output
403 - Plan Insufficient
403 - Plan Insufficient
- Your organization doesn’t have API access
- Upgrade to API plan or higher
- Contact sales for enterprise options
