> ## Documentation Index > Fetch the complete documentation index at: https://docs.qumo-deploy.com/llms.txt > Use this file to discover all available pages before exploring further. # List an identity's IP allowlist > Lists the identity's IP allowlist entries, oldest first. With no entries the identity's tokens work from any address; with any, only from addresses inside one of them. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v1/projects/{project_id}/identities/{identity_id}/ip-allowlists openapi: 3.1.0 info: title: Qumo Deploy REST API description: > The Qumo Deploy control plane: organizations, projects, signing keys, machine identities, access control, audit and billing. Relay credentials are not issued here: your app signs them with its own [signing keys](/guides/signing-keys). Every operation here is generated against the routes the server registers and checked in CI, so an operation in this reference exists and a route missing from it is deliberately internal (relay mesh, webhooks, probes, operator-only and browser sign-in routes). Errors are JSON objects with one `error` field. What each status code means is in [Error codes](/guides/error-codes); the token scope each permission needs is in [Scopes and permissions](/guides/scopes-permissions). version: 1.0.0 servers: - url: https://api.qumo-deploy.com description: Public API (Bearer tokens only; cookies are ignored) security: [] tags: - name: Account description: The signed-in user's own sessions, tokens, security settings and data. - name: Device flow description: OAuth 2.0 device authorization, used by `qumod login`. - name: Organizations description: Organizations, their members and usage. - name: Projects description: Projects inside an organization. - name: Signing keys description: Keys your app signs relay credentials with. - name: Relays description: Where clients of a broadcast path connect. - name: Identities description: Machine identities, their tokens and IP allowlists. - name: Access control description: Roles, IAM bindings and invitations. - name: Audit description: The audit log and its webhook. - name: Notifications description: Notification policies. - name: Billing description: Plans, usage cost, budgets, invoices and payment methods. - name: Pricing description: Public price list. paths: /v1/projects/{project_id}/identities/{identity_id}/ip-allowlists: get: tags: - Identities summary: List an identity's IP allowlist description: | Lists the identity's IP allowlist entries, oldest first. With no entries the identity's tokens work from any address; with any, only from addresses inside one of them. operationId: listIdentityIpAllowlists parameters: - name: project_id in: path required: true description: The project's id. schema: type: string format: uuid example: 9b1d6e2f-4a3c-4f8b-a7e5-0c9d2b4f6e81 - name: identity_id in: path required: true description: The identity's id. schema: type: string format: uuid example: c2a4e6f8-0b1d-4c3e-9f5a-7b9d1e3f5a6c responses: '200': description: The identity's allowlist entries. content: application/json: schema: $ref: '#/components/schemas/IpAllowlistList' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' security: - token: [] - cliSession: [] - sessionCookie: [] components: schemas: IpAllowlistList: type: object required: - ip_allowlists properties: ip_allowlists: type: array items: $ref: '#/components/schemas/IpAllowlistEntry' IpAllowlistEntry: type: object description: A range an identity's tokens may be used from. required: - id - identity_id - cidr - label - created_at properties: id: type: string format: uuid example: 4e6a8c0d-2f4b-4a7e-8c1d-3b5f7a9c1e2d identity_id: type: string format: uuid example: c2a4e6f8-0b1d-4c3e-9f5a-7b9d1e3f5a6c cidr: type: string description: The range, normalized to its network address. example: 203.0.113.0/24 label: type: string example: Office network created_at: type: string format: date-time example: '2026-10-14T09:20:31Z' Error: type: object required: - error properties: error: type: string description: A human-readable message. example: organization_id is required responses: BadRequest: description: >- Malformed request or failed validation. See [Error codes](/guides/error-codes). content: application/json: schema: $ref: '#/components/schemas/Error' Unauthorized: description: Missing or invalid credentials. See [Error codes](/guides/error-codes). content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: >- Authenticated but not allowed (permission, token scope, IP allowlist or CSRF). See [Error codes](/guides/error-codes). content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: token: type: http scheme: bearer bearerFormat: qumo_pat_ description: > A personal access token (`POST /v1/auth/tokens`) or a machine identity token (`POST /v1/projects/{project_id}/identities/{identity_id}/tokens`), both prefixed `qumo_pat_`. A token's scopes cap what it can do; see [Scopes and permissions](/guides/scopes-permissions). A personal token names no organization: on a route whose path names no project or organization, pass `?organization_id=`. cliSession: type: http scheme: bearer description: | The session token `qumod login` obtains through the device flow (`POST /v1/auth/device/token`). It acts as the signed-in user, like a console session, and needs no CSRF token. sessionCookie: type: apiKey in: cookie name: __Host-qumo_session description: | The console's browser session. Accepted only on the console origin (`https://console.qumo-deploy.com`), never on `api.qumo-deploy.com`. A request that changes state must also send `X-CSRF-Token`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.