> ## 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. # Export account data > Downloads the personal data held about the signed-in user: profile, linked sign-in identities, sessions, GitHub connection and role bindings. Served as a JSON file attachment. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v1/users/me/export 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/users/me/export: get: tags: - Account summary: Export account data description: | Downloads the personal data held about the signed-in user: profile, linked sign-in identities, sessions, GitHub connection and role bindings. Served as a JSON file attachment. operationId: exportAccountData responses: '200': description: The user's data. headers: Content-Disposition: description: Marks the response as a file download. schema: type: string example: attachment; filename="qumo_user_export.json" content: application/json: schema: $ref: '#/components/schemas/AccountExport' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' security: - cliSession: [] - sessionCookie: [] components: schemas: AccountExport: type: object required: - user - identities - sessions - iam_bindings properties: user: $ref: '#/components/schemas/AccountUser' identities: type: array description: The sign-in identities linked to the account. items: $ref: '#/components/schemas/AccountExportIdentity' sessions: type: array items: $ref: '#/components/schemas/AccountExportSession' github_connection: type: object description: The linked GitHub account. Absent when none is linked. required: - github_login properties: github_login: type: string example: hanasato iam_bindings: type: array description: The roles the user holds. items: $ref: '#/components/schemas/AccountExportIamBinding' AccountUser: type: object required: - id - email - name - avatar_url - created_at - updated_at properties: id: type: string format: uuid example: 5e7a9c3b-1d2f-4b6e-8a0c-7f3d9e1b5a24 email: type: string format: email example: hana@example.com name: type: string example: Hana Sato avatar_url: type: - string - 'null' format: uri example: https://avatars.example.com/u/5e7a9c3b.png created_at: type: string format: date-time example: '2026-06-12T03:40:00Z' updated_at: type: string format: date-time example: '2026-10-30T11:02:18Z' onboarded_at: type: string format: date-time description: When the user completed onboarding. Absent until then. example: '2026-06-12T03:46:51Z' AccountExportIdentity: type: object required: - provider - provider_id properties: provider: type: string description: The sign-in provider. example: google provider_id: type: string description: The user's id at that provider. example: '108234567890123456789' AccountExportSession: type: object required: - id - expires_at - created_at - ip_address - user_agent properties: id: type: string pattern: ^[0-9a-f]{64}$ example: 4f2a9c1e7b3d5a8f0e6c2b9d1a7f3e5c8b0d4a6f2e9c1b7d3a5f8e0c6b2d9a14 expires_at: type: string format: date-time example: '2026-11-08T22:05:10Z' created_at: type: string format: date-time example: '2026-11-01T22:05:10Z' ip_address: type: - string - 'null' example: 203.0.113.24 user_agent: type: - string - 'null' example: qumod/0.9.0 AccountExportIamBinding: type: object required: - id - role_id - scope_type - scope_id properties: id: type: string format: uuid example: a1c3e5f7-9b2d-4f6a-8c0e-2d4f6a8b0c1e role_id: type: string example: roles/organization.admin scope_type: type: string enum: - platform - organization - project example: organization scope_id: type: string example: 3f8c2a1e-7b4d-4e9a-9c61-2d5e8f0a1b7c Error: type: object required: - error properties: error: type: string description: A human-readable message. example: organization_id is required responses: 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: 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.