> ## Documentation Index
> Fetch the complete documentation index at: https://docs.frankieone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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 ](https://github.com/ulid/spec) (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

<Callout icon="bell" color="#FFCA16" iconType="regular">
  Always store the Request ID with your transaction records. It's the primary
  key for tracking API interactions with FrankieOne.
</Callout>

## Best Practices

<CardGroup cols={2}>
  <Card title="Record Keeping" icon="database">
    Store Request IDs alongside your transaction records for future reference
    and auditing.
  </Card>

  <Card title="Troubleshooting" icon="bug">
    When contacting support, always provide the Request ID for faster problem
    resolution.
  </Card>
</CardGroup>

<Callout icon="star" color="#3DD892" iconType="regular">
  ##### Developer Tip

  Consider implementing a logging system that automatically captures and indexes
  Request IDs for easy searching and retrieval.
</Callout>