RequestID
Every API response includes a unique Request ID (also known as a Transaction ID) that helps track and troubleshoot API calls. We implement this using ULID (Universally Unique Lexicographically Sortable Identifier).
What makes Request IDs special?
- Time-based UUID with millisecond precision timestamp
- Contains a random element for uniqueness
- Sortable alphabetically and chronologically
- Guaranteed unique across all API calls
Using Request IDs
You can use Request IDs to:
- Track API calls in your system
- Retrieve historical API call results
- Debug issues with FrankieOne support
- Maintain audit trails
Always store the Request ID with your transaction records. It’s the primary key for tracking API interactions with FrankieOne.
Best Practices
Record Keeping
Store Request IDs alongside your transaction records for future reference and auditing.
Troubleshooting
When contacting support, always provide the Request ID for faster problem resolution.
Developer Tip
Consider implementing a logging system that automatically captures and indexes Request IDs for easy searching and retrieval.