> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/api-reference/authentication/fetch-api-keys.md).
# GET /keys
List your API keys
List your API keys.
`operationId`: `fetchApiKeys`
> **Declared server:** `https://api.testnet.nexus.xyz/v1`. See [Networks](/api-reference/guides/networks.md).
> **Not reachable through CCXT.** Session/credential lifecycle. CCXT takes credentials as constructor config; it never mints them.
**Authentication:** `bearerAuth`.
## List your API keys
> Returns key IDs and tiers for all keys owned by the authenticated wallet. Secrets are not included. Scoped to the network serving this request: keys minted on another network are not listed here, and their absence is not evidence that they were deleted or that they are inactive on the network that minted them.
```json
{"openapi":"3.1.0","info":{"title":"Nexus Exchange API","version":"0.9.101"},"tags":[{"name":"Authentication","description":"EVM wallet sign-in and API key management"}],"servers":[{"url":"https://api.testnet.nexus.xyz/v1","description":"Public testnet (play funds) — the default server and /v1 transport base for unversioned paths."},{"url":"https://api.nexus.xyz/v1","description":"Mainnet — **REAL FUNDS**. Collateral is USDX bridged from Ethereum Mainnet; orders placed here move real money, and there is no faucet. The durable per-network base. Listed after testnet on purpose, so nothing that reaches for \"the first https server\" lands on the real-funds target. Not resolvable yet: DNS/TLS is a separate infra change."},{"url":"http://localhost:9090","description":"Local development — the indexer served directly. Not a public network; whatever your local instance holds."}],"security":[{"bearerAuth":[]}],"components":{"securitySchemes":{"bearerAuth":{"type":"http","scheme":"bearer","description":"Session token from POST /auth/login. Used only for API key management (/keys endpoints). Session tokens are network-scoped exactly like API keys: a token from one network's `POST /auth/login` is not valid on another, so sign in and manage keys on the same host you intend to trade against."}},"schemas":{"KeyInfo":{"type":"object","description":"An API key as `GET /keys` lists it. Carries no secret: the secret exists only in the `CreateKeyResponse` returned at creation.","required":["key_id","tier","label","created_at_ms","expires_at_ms"],"properties":{"key_id":{"type":"string","description":"Public key identifier, `nx_` + 16 lowercase hex characters."},"tier":{"$ref":"#/components/schemas/Tier"},"label":{"type":["string","null"],"description":"Caller-supplied label from `POST /keys`, or `null` for a key created without one. **Nullable, not optional** — the field is always present, so read `null` rather than branching on a missing key."},"created_at_ms":{"allOf":[{"$ref":"#/components/schemas/TimestampMs"}],"description":"When the key was minted. The list is ordered by this value, oldest first."},"expires_at_ms":{"type":["integer","null"],"format":"int64","description":"Unix ms after which this key stops authenticating, or `null` if it never expires. **Nullable, not optional** — the field is always present, so read `null` rather than branching on a missing key. Set from `POST /keys`'s optional `ttl_ms`; enforced for Postgres-backed keys, the only backend live today."}}},"Tier":{"type":"string","enum":["Pro","MarketMaker","Unlimited"],"description":"Rate-limit tier of an API key or account override. Exactly three values, PascalCase on the wire.\n\n`Pro` is what any owner with no override resolves to. `MarketMaker` carries the market-making allowance. `Unlimited` is for gateway/proxy keys that multiplex many users and is exempt from per-key rate limiting — it is a value a client can really receive, so a two-value union over `Pro` and `MarketMaker` is wrong.\n\n`PUT /admin/tiers` ACCEPTS a laxer input vocabulary than this (`pro`, `market_maker`, `marketmaker` and `unlimited` all parse), but every response normalizes to the three values above."},"TimestampMs":{"type":"integer","format":"int64","description":"Unix epoch timestamp in milliseconds."}}},"paths":{"/keys":{"get":{"operationId":"fetchApiKeys","tags":["Authentication"],"summary":"List your API keys","description":"Returns key IDs and tiers for all keys owned by the authenticated wallet. Secrets are not included. Scoped to the network serving this request: keys minted on another network are not listed here, and their absence is not evidence that they were deleted or that they are inactive on the network that minted them.","responses":{"200":{"description":"The session's API keys.","content":{"application/json":{"schema":{"type":"array","items":{"$ref":"#/components/schemas/KeyInfo"}}}}},"401":{"description":"Valid session token required"}}}}}}
```
***
API version `0.9.131`
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nexus.xyz/api-reference/authentication/fetch-api-keys.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.