> ## Documentation Index > Fetch the complete documentation index at: https://docs.factrove.app/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Describe what the running code does. Do not invent hosted pricing, launch dates, or security guarantees. Share and viewer links are a configured base URL plus an artifact path. Show localhost and a placeholder origin such as https://library.example.com. # Create an API key > Requires a browser session. Do not send `Authorization`. A request that also sends it is 401 with message `API key management requires a browser session.` Cookie writes need `Origin` or `Referer` to be `WEB_ORIGIN` or `PUBLIC_BASE_URL`. A missing or different origin is 403 `FORBIDDEN` before Better Auth runs. The secret is returned once in `key`. The plugin stores only a hash. Keys use the `ftrv_` prefix and do not expire. The plugin's own per-key rate limit is off. ## OpenAPI ````yaml /api-reference/openapi.json post /api/auth/api-key/create openapi: 3.1.0 info: title: Factrove HTTP API version: 0.1.0 description: >- Generated from `@factrove/contracts` schemas and the HTTP operation catalog. Product routes live under `/api/v1`. Auth and API key management live under `/api/auth`. Do not treat this file as hand-written. Run `pnpm docs:openapi` after contract or route-catalog changes. servers: - url: http://localhost:3001 description: Local development API origin - url: https://api.example.com description: Example self-hosted API origin security: [] tags: - name: Health description: Process liveness. - name: Auth description: Sessions and API keys. - name: Artifacts description: Upload, list, rename, delete, detail, and content. - name: Shares description: Owner public-link and password controls. - name: Public description: Anonymous share detail, unlock, and HTML. paths: /api/auth/api-key/create: post: tags: - Auth summary: Create an API key description: >- Requires a browser session. Do not send `Authorization`. A request that also sends it is 401 with message `API key management requires a browser session.` Cookie writes need `Origin` or `Referer` to be `WEB_ORIGIN` or `PUBLIC_BASE_URL`. A missing or different origin is 403 `FORBIDDEN` before Better Auth runs. The secret is returned once in `key`. The plugin stores only a hash. Keys use the `ftrv_` prefix and do not expire. The plugin's own per-key rate limit is off. operationId: createApiKey requestBody: required: true description: A name is required, 1 to 32 characters. content: application/json: schema: $ref: '#/components/schemas/CreateApiKeyRequest' example: name: cli responses: '200': description: The new key, including `key` once. content: application/json: schema: $ref: '#/components/schemas/CreateApiKeyResponse' example: id: key_example name: cli start: ftrv_example1 key: ftrv_example_key_shown_once '400': description: >- Empty or missing name is Better Auth `NAME_REQUIRED` (`API Key name is required.`). A name longer than 32 characters is `INVALID_NAME_LENGTH`. '401': description: No browser session, or Authorization was also sent. '403': description: >- Cookie write whose Origin or Referer is not WEB_ORIGIN or PUBLIC_BASE_URL. Code `FORBIDDEN`. content: application/json: schema: $ref: '#/components/schemas/ApiError' example: error: code: FORBIDDEN message: This request origin is not allowed. security: - sessionCookie: [] x-codeSamples: - lang: bash label: Sign in and create a key source: |- api=http://localhost:3001 origin=http://localhost:3000 jar=$(mktemp) curl -sS -c "$jar" -X POST "$api/api/auth/sign-up/email" \ -H "Content-Type: application/json" \ -H "Origin: $origin" \ -d '{"name":"Local Owner","email":"owner@example.com","password":"replace-this-password"}' curl -sS -b "$jar" -X POST "$api/api/auth/api-key/create" \ -H "Content-Type: application/json" \ -H "Origin: $origin" \ -d '{"name":"cli"}' - lang: javascript label: Browser on the web origin source: >- const response = await fetch("http://localhost:3001/api/auth/api-key/create", { method: "POST", credentials: "include", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ name: "cli" }), }); components: schemas: CreateApiKeyRequest: type: object properties: name: type: string minLength: 1 maxLength: 32 required: - name additionalProperties: false CreateApiKeyResponse: type: object properties: id: type: string name: type: string key: type: string start: anyOf: - type: string - type: 'null' required: - id - key additionalProperties: {} ApiError: type: object properties: error: type: object required: - code - message additionalProperties: false properties: code: type: string enum: - INVALID_REQUEST - ORGANIZATION_REQUIRED - ORGANIZATION_CHANGED - UNAUTHENTICATED - PASSWORD_REQUIRED - PASSWORD_INCORRECT - FORBIDDEN - ARTIFACT_NOT_FOUND - CONTENT_CONFLICT - FILE_TOO_LARGE - CONTENT_TOO_LARGE - UNSUPPORTED_FILE_TYPE - CONTENT_TOO_COMPLEX - RATE_LIMITED - INTERNAL_ERROR - STORAGE_UNAVAILABLE - CONVERSION_UNAVAILABLE - UNLOCK_UNAVAILABLE description: >- 400/404 INVALID_REQUEST: The request is missing a required field, has the wrong shape, or failed validation. Typical causes are a missing file, an invalid access type, view, format, or artifact id, or invalid UTF-8. Unmatched non-public product routes also return 404 INVALID_REQUEST with message Not found. 400 ORGANIZATION_REQUIRED: The caller asked to share with an organization but has no current organization membership. Upload with accessType org_shared and PATCH /api/v1/artifacts/{id} for a private artifact both use this code. 409 ORGANIZATION_CHANGED: PATCH /api/v1/artifacts/{id} for a private artifact named an organizationId that is not the caller's current membership when the conditional UPDATE reads, or a deadlock, serialization failure, or lock timeout persisted after one retry. The artifact is not written. That UPDATE is the linearization point: an authorization change that commits after its snapshot can land before commit and does not cancel the share. About 16 seconds is the budget for the two attempts, not an endpoint deadline. An artifact that is already org_shared returns 200 instead. 401 UNAUTHENTICATED: The product route needs a session cookie or Authorization: Bearer API key, and neither was accepted. PATCH /api/v1/artifacts/{id} also returns this when the session was revoked or expired before the conditional update read it, and does not write. A revocation that commits after that snapshot does not cancel the share. 401 PASSWORD_REQUIRED: The public share is password protected and the request did not present a valid unlock grant or content ticket. 401 PASSWORD_INCORRECT: The password sent to the public unlock route did not match. 403 FORBIDDEN: A cookie-authenticated write used an Origin or Referer that is not WEB_ORIGIN or PUBLIC_BASE_URL. 404 ARTIFACT_NOT_FOUND: The artifact id is unknown, the caller cannot read it, or the public share token is not active. Rename and delete also use this body when the caller is not the creator, including an organization admin or another member who can read an org_shared artifact. Those cases share this body. 409 CONTENT_CONFLICT: Another replace of the same artifact revision finished first. Upload again to replace the current content. Delete returns this code when concurrent replaces prevent deletion after eight attempts. Retry DELETE. 413 FILE_TOO_LARGE: The upload is larger than the 10 MiB HTML limit. A JSON body larger than 102,400 bytes uses the same code with message The request is too large. 413 CONTENT_TOO_LARGE: Stored HTML is larger than the Markdown conversion input limit. 415 UNSUPPORTED_FILE_TYPE: The upload is not a .html or .htm file. 422 CONTENT_TOO_COMPLEX: Markdown conversion exceeded its time, memory, nesting, or output limit. 429 RATE_LIMITED: Too many public views from one client address, or too many password attempts. Password-attempt 429 responses include Retry-After. Public-view 429 responses do not. 500 INTERNAL_ERROR: An unexpected persistence or service failure. 503 STORAGE_UNAVAILABLE: Object storage failed. A failed upload leaves no artifact row. A failed artifact delete keeps the row. The object may already be gone, so retry DELETE. 503 CONVERSION_UNAVAILABLE: The Markdown conversion worker pool is full. This response does not include Retry-After. 503 UNLOCK_UNAVAILABLE: Password verification is busy because the process-wide Argon2 gate is saturated or every remaining share check slot is in flight. Includes Retry-After. message: type: string required: - error additionalProperties: false description: >- Product error envelope. Better Auth `/api/auth` routes may return a different JSON shape. securitySchemes: sessionCookie: type: apiKey in: cookie name: better-auth.session_token description: >- Better Auth session cookie from email/password sign-in. On an https API origin the name is `__Secure-better-auth.session_token`. On http it is `better-auth.session_token`. Host-only unless AUTH_COOKIE_DOMAIN is set. Use a cookie jar instead of typing the name. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.