> ## Documentation Index > Fetch the complete documentation index at: https://docs.withsplendor.com/llms.txt > Use this file to discover all available pages before exploring further. # List platform API keys > Lists your platform's API keys with their creation, revocation, and last-used timestamps. The secret token itself is shown only once, when the key is created. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/platform/keys openapi: 3.1.0 info: description: >- Splendor is a search and retrieval API for your operational data. Ingest datasets — logs, documents, and structured records — and query them through one consistent interface that spans full-text, SQL, and semantic (vector) search. Every request authenticates with a bearer token and selects a workspace with the `X-Splendor-Tenant-Id` header. Read and query operations are available to any member; operations that create, change, or delete data require an admin role. All search modes return one shared envelope, and every result carries provenance back to the exact source object it came from. title: Splendor API version: 1.0.0 servers: - description: Production url: https://api.withsplendor.com security: - bearerAuth: [] tags: - description: Resolve the authenticated user and the tenants they can access. name: Identity - description: >- Build on Splendor as a platform: authenticate with a platform API key to provision an isolated tenant per end-customer and manage your platform keys. name: Platform - description: >- List datasets, inspect inferred schemas and readiness, and manage dataset lifecycle including deletion and schema rebuilds. name: Datasets & schema - description: >- Run full-text, SQL, and semantic search over your datasets, stream results, and resolve object media. name: Search & query - description: Save queries and materialize result sets for repeatable analysis. name: Views - description: >- Define named, versioned, parameterized SQL queries and manage their versions. name: Query Endpoints - description: Create and manage asynchronous exports of search results. name: Exports - description: >- Configure data sources, upload data through hosted multipart uploads, stream logs, and track ingest runs. name: Sources & ingest - description: >- Connect third-party systems by managing connector instances in the selected tenant. name: Connectors - description: Define and test detection rules that run against incoming data. name: Detections - description: Inspect discovered fields and promote them to fast, aggregatable fields. name: Fields - description: >- Operational visibility and recovery: audit logs, usage, dead-letter queue, reindex jobs, and data-deletion jobs. name: Operations paths: /v1/platform/keys: get: tags: - Platform summary: List platform API keys description: >- Lists your platform's API keys with their creation, revocation, and last-used timestamps. The secret token itself is shown only once, when the key is created. operationId: listPlatformKeys responses: '200': content: application/json: schema: $ref: '#/components/schemas/PlatformKeyListResponse' description: Successful Response '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '503': content: application/json: schema: $ref: '#/components/schemas/ApiError' description: A required backend is temporarily unavailable. components: schemas: PlatformKeyListResponse: example: keys: - created_at: '2026-01-15T09:30:00Z' id: 1 last_used_at: '2026-01-15T09:30:00Z' name: production revoked_at: null token: null properties: keys: items: $ref: '#/components/schemas/PlatformKeyResponse' title: Keys type: array required: - keys title: PlatformKeyListResponse type: object ApiError: description: >- Error envelope returned by every Splendor API endpoint. ``detail`` is either a plain message string (most errors) or a structured ``{code, message}`` object (validation and capacity errors that carry a stable machine-readable code). examples: - detail: Dataset not found - detail: code: semantic_search_capacity_exhausted message: Semantic search capacity is temporarily exhausted; retry shortly. properties: detail: anyOf: - type: string - $ref: '#/components/schemas/ErrorBody' title: Detail required: - detail title: ApiError type: object PlatformKeyResponse: description: >- A platform API key. The plaintext ``token`` is returned only when the key is minted; thereafter only the metadata is retrievable. example: created_at: '2026-01-15T09:30:00Z' id: 1 last_used_at: '2026-01-15T09:30:00Z' name: production revoked_at: null token: splpk.v1.cG9vbC1kYXk.EXAMPLE-secret-shown-once properties: created_at: format: date-time title: Created At type: string id: title: Id type: integer last_used_at: anyOf: - format: date-time type: string - type: 'null' title: Last Used At name: title: Name type: string revoked_at: anyOf: - format: date-time type: string - type: 'null' title: Revoked At token: anyOf: - type: string - type: 'null' title: Token required: - id - name - created_at title: PlatformKeyResponse type: object ErrorBody: description: Structured error detail returned by validation and capacity errors. examples: - code: semantic_query_text_required message: Semantic vector search requires non-empty text. properties: code: title: Code type: string message: title: Message type: string required: - code - message title: ErrorBody type: object responses: Unauthorized: content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The bearer token is missing, malformed, or expired. Forbidden: content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The token lacks access to the tenant or the role required. securitySchemes: bearerAuth: bearerFormat: JWT description: API token issued from the Splendor console. scheme: bearer type: http ````