> For the complete documentation index, see [llms.txt](https://docs.abyiss.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abyiss.com/crypto-api/references/return-types.md).

# Return Types

## Timestamps

`"timestamp": "1639333070818"`

Unless otherwise specified, all timestamps from our API are retuned in [Unix ](https://en.wikipedia.org/wiki/Unix_time)time as strings. Make sure you can parse the following Unix format. You can reference Unix timestamp conversion tools if needed [here](https://www.unixtimestamp.com/index.php).&#x20;

## IDs

`"id": "1029807859"`

All identifiers are returned as strings and are exchange specific. Meaning all id's are unique to each individual crypto exchange.&#x20;

To learn more about the id's returned by our API, you will have to research each individual exchanges documentation. Every id has a different meaning on each exchange.

## Nonce

`"nonce": 15624599412`

Nonce are returned as strings and are exchange specific, similar to id's. Meaning all nonce are unique to each individual crypto exchange. To learn more about the nonce returned by our API, you will have to research each individual exchanges documentation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.abyiss.com/crypto-api/references/return-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
