> ## Documentation Index > Fetch the complete documentation index at: https://developers.logicgate.ai/llms.txt > Use this file to discover all available pages before exploring further. # Create a new user-managed API token > Creates a named API token for the current user and returns the plaintext access token and refresh token exactly once. Neither can be recovered from the server afterward, so the caller must persist both values before navigating away. The refresh token can be used against POST /api/v2/account/token to obtain a fresh access token without re-creating from the UI. ## OpenAPI ````yaml POST /api/v1/account/tokens openapi: 3.1.0 info: title: Risk Cloud API (Legacy v1) — Auth description: >- The Risk Cloud API is a collection of RESTful API endpoints that empower you and your team to directly integrate, automate, and build with the Risk Cloud. Risk Cloud API endpoint payloads are JSON based, with some endpoints supporting exports in CSV and XSLX formats for flexible integration. This API documentation showcases our Risk Cloud API v1, containing a variety of endpoints with continued support for enabling integrations with the Risk Cloud. Visit the [LogicGate Risk Cloud Developer Portal](https://www.logicgate.com/developer/) to get started with building your custom integration with quick start guides, usage guides, release notes, and more. Or download the [v1 OpenAPI specification](/legacy-openapi.json). Explore our [Risk Cloud API v2](https://docs.logicgate.com/v2/index.html) endpoints and documentation as well. [Risk Cloud API v2](https://docs.logicgate.com/v2/index.html) is our collection of API-First endpoints that are tailor made for our developer users, offer concise and highly documented details, are supported by a [Postman collection](https://www.postman.com/logicgate-postman/workspace/logicgate-risk-cloud-api/collection/29257227-de8d264b-6eeb-4177-bea6-2da0a8cabffc) and [v2 OpenAPI specification](https://github.com/LogicGateTech/openapi), and contain our latest API endpoint releases. contact: name: developer-relations@logicgate.com email: developer-relations@logicgate.com version: v2026.8.2 servers: - url: https://{subdomain}.logicgate.com description: Your Risk Cloud environment. variables: subdomain: default: your-instance description: Your Risk Cloud environment's subdomain (e.g. `qa`). security: - ApiToken: [] - basic: [] tags: - name: Authentication description: >- Getting Started: How to create an [API Access Token](https://www.logicgate.com/developer/risk-cloud-api-authentication/) to begin integrating with the Risk Cloud API - name: Principal description: >- Endpoints for the authenticated principal to view and manage their own details. - name: SCIM description: >- SCIM (System for Cross-domain Identity Management) endpoints for provisioning and managing Users and Groups from an external identity provider. - name: External User description: >- Endpoints for creating and managing external (non-employee) users who access Risk Cloud via record-scoped tokens rather than standard login. - name: Account description: >- Endpoints for retrieving details about the current Risk Cloud account/environment. externalDocs: description: Developer Portal url: https://www.logicgate.com/developer/ paths: /api/v1/account/tokens: post: tags: - Authentication summary: Create a new user-managed API token description: >- Creates a named API token for the current user and returns the plaintext access token and refresh token exactly once. Neither can be recovered from the server afterward, so the caller must persist both values before navigating away. The refresh token can be used against POST /api/v2/account/token to obtain a fresh access token without re-creating from the UI. operationId: createToken parameters: - name: Authorization in: header description: >- A bearer authorization header containing a Risk Cloud API access token in the format `Authorization: Bearer TOKEN` — replace `TOKEN` with your actual access token. To obtain a Risk Cloud API access token, refer to [Obtain an API Access Token](https://www.logicgate.com/developer/risk-cloud-api-authentication/) in the [LogicGate Help Center](https://help.logicgate.com/hc/en-us). required: true schema: type: string example: Bearer TOKEN requestBody: content: application/json: schema: $ref: '#/components/schemas/CreateUserApiTokenIn' required: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/UserApiTokenCreatedOut' components: schemas: CreateUserApiTokenIn: type: object description: Request body for creating a new user-managed API token. properties: name: type: string description: Human-readable label for the token (e.g. "My Zapier integration"). maxLength: 100 minLength: 0 required: - name UserApiTokenCreatedOut: type: object description: >- Newly created token including the one-time plaintext access and refresh secrets. Neither plaintext can be retrieved later. properties: accessToken: type: string description: The access token to use as a Bearer credential. Shown once. refreshToken: type: string description: >- The refresh token to use against POST /api/v2/account/token to create a fresh access token without UI re-creation. Shown once. token: $ref: '#/components/schemas/UserApiTokenOut' description: >- The persisted token row's metadata. Mirrors a single row from GET /api/v1/account/tokens so a client can populate the Access Keys table without a follow-up request after creation. UserApiTokenOut: type: object description: Metadata for a user-managed API token (no secret). properties: id: type: string description: Token id name: type: string description: Human-readable label set at creation created: type: string format: date-time description: Timestamp the token was minted expiresAt: type: string format: date-time description: Timestamp the token expires lastUsedAt: type: string format: date-time description: >- Timestamp of the last successful authentication using this token; null if never used securitySchemes: ApiToken: type: http scheme: bearer bearerFormat: API Token description: Bearer token issued via the Authentication endpoints. basic: type: http scheme: basic description: >- HTTP Basic auth using base64-encoded Client Key:Secret Key credentials, used only to obtain or refresh a bearer token via the Authentication endpoints. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.