> ## Documentation Index > Fetch the complete documentation index at: https://docs.peridot.id/llms.txt > Use this file to discover all available pages before exploring further. # Rotate the on-chain authority to a registered replacement credential > Credential-lifecycle rotation: register the replacement credential first (approval flow), then the current key authorizes on-chain `update_authority` here. The old credential is revoked in DB only after the chain confirms the new authority. ## OpenAPI ````yaml /openapi.yaml post /wallet/rotate openapi: 3.0.3 info: title: PeridotID API version: 0.1.0 description: > Gaming Identity Platform — Authentication, Identity, and Profile for the Peridot ecosystem. ## Base URL All endpoints are prefixed with `/v1`. | Environment | Base URL | |---|---| | Production | `https://api.pid.peridotvault.com/v1` | | Local dev | `http://localhost:3300/v1` | ## Authentication Authentication is **cookie-based**. After a successful Google sign-in the API sets two `HttpOnly` cookies: - `pid_access` — short-lived JWT access token (15 min), sent on every request. - `pid_refresh` — long-lived rotating refresh token (30 days), only sent to `/v1/auth`. Browsers handle these automatically; non-browser clients must send `Cookie: pid_access=` on each request and call `/v1/auth/refresh` before the access token expires. contact: name: PeridotID license: name: MIT url: https://opensource.org/licenses/MIT servers: - url: https://api.pid.peridotvault.com/v1 description: Production - url: http://localhost:3300/v1 description: Local development security: [] tags: - name: auth description: Login, logout, token refresh, and machine (client-credentials) tokens - name: identity description: The user's identity across products - name: profile description: The user's public profile - name: wallet description: > The user's wallet, associated with their PID. **Deprecated (V3 surface)** — preserved for existing clients, backed by `linked_address` chain accounts. Use `/account` and the smart account instead. - name: account description: >- PeridotID account — owns chain accounts (smart account PDA, legacy linked address) - name: fiat description: | The internal IDR fiat ledger: balances, statements, sends, and money-in. Top-ups enter through a hosted DOKU Checkout page (no Sub-Account) and credit the internal ledger once the payment is corroborated. Any identity can send to any identity (escrow/payouts). Fees: global 0.1% (min Rp100, no cap) plus optional per-app fees that stack and credit the app. Bank withdrawals (redemption) are disabled for now. - name: apps description: | Third-party apps ("Sign in with PeridotID"): client_id, allowed origins, optional backend secret, ledger callbacks (deferred), and a per-app fee schedule. Owner-scoped — a non-owner gets 404. App backends authenticate server-side with `POST /v1/auth/token` (client credentials). - name: credentials description: > Signing authorities (secp256r1 passkeys). Google OAuth proves identity; a passkey authorizes the wallet. The first credential registers freely; each additional credential requires approval by an existing credential (existing-credential approval rule). - name: permissions description: > EVM permission grants (scoped P-256 session keys, WHITEPAPER.md §10). Validation is pure hygiene + canonical id/challenge computation; submission-time account binding is enforced by the relay path. - name: session-keys description: > SVM gameplay sessions (Ed25519 session keys in isolated PDAs, WHITEPAPER.md §11). Validation is pure hygiene + canonical address/challenge computation; submission-time vault binding is enforced by the relay path. - name: openapi description: Machine-readable API specification paths: /wallet/rotate: post: tags: - wallet summary: Rotate the on-chain authority to a registered replacement credential description: > Credential-lifecycle rotation: register the replacement credential first (approval flow), then the current key authorizes on-chain `update_authority` here. The old credential is revoked in DB only after the chain confirms the new authority. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/RotateAuthority' responses: '200': description: Rotation result content: application/json: schema: type: object required: - signature - status properties: signature: type: string status: type: string enum: - confirmed - pending '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/RateLimited' security: - cookieAuth: [] components: schemas: RotateAuthority: type: object required: - oldCredentialId - newCredentialId - nonce - expiry - assertion properties: oldCredentialId: type: string description: Credential ID of the current (signing) authority newCredentialId: type: string description: Credential ID of the already-registered replacement authority nonce: type: string description: Chain nonce the current key signed against expiry: type: integer description: Chain-time expiry (unix seconds, TTL ≤ 600s) assertion: $ref: '#/components/schemas/PasskeyAssertion' PasskeyAssertion: type: object required: - id - signature - authenticatorData - clientDataJSON properties: id: type: string description: Credential ID that produced the assertion signature: type: string description: base64url 64-byte r‖s secp256r1 signature authenticatorData: type: string description: base64url authenticatorData clientDataJSON: type: string description: base64url clientDataJSON (challenge = domain payload) ApiError: type: object required: - statusCode - message properties: statusCode: type: integer message: oneOf: - type: string - type: array items: type: string responses: BadRequest: description: Validation error content: application/json: schema: $ref: '#/components/schemas/ApiError' example: statusCode: 400 message: - >- handle must be 3-20 chars: lowercase letters, numbers, underscore Unauthorized: description: Missing, expired, or invalid access/refresh token content: application/json: schema: $ref: '#/components/schemas/ApiError' example: statusCode: 401 message: Unauthorized NotFound: description: The identity or profile does not exist content: application/json: schema: $ref: '#/components/schemas/ApiError' example: statusCode: 404 message: No Identity found RateLimited: description: Too many requests content: application/json: schema: $ref: '#/components/schemas/ApiError' example: statusCode: 429 message: 'ThrottlerException: Too Many Requests' securitySchemes: cookieAuth: type: apiKey in: cookie name: pid_access description: JWT access token set by /auth/google/callback or /auth/refresh ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.