docs: update auth signed retry examples

[DhruvPareek]

Summary

• Update signed-retry snippets and OpenAPI examples to use Request:<uuid> request IDs.
• Replace base64/requestId-shaped payloadToSign examples with canonical compact JSON Turnkey activity payloads.
• Fix the export curl continuation in the wallet export snippet.

Test Plan

• make build
• git diff --check
• Targeted rg scan for stale base64 payloads, bare UUID Request-Id headers, and old signed-retry payload shapes.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
grid-flow-builder	Ready	Preview, Comment	May 19, 2026 8:38pm

[DhruvPareek]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• docs: align auth endpoint docs with PDF #481
• docs: allow multiple passkey credentials #479
• docs: update auth signed retry examples #477 👈 (View in Graphite)
• docs: fix auth account identifiers #476
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Greptile Summary

This PR updates auth signed-retry documentation examples across MDX snippets and OpenAPI specs, replacing placeholder base64 payloads and bare-UUID request IDs with realistic Turnkey activity JSON payloads and Request:<uuid>-formatted IDs.

• Updates payloadToSign examples in authentication.mdx, exporting-wallet.mdx, managing-sessions.mdx, and four OpenAPI path/component files from opaque base64 blobs to canonical compact Turnkey activity JSON bodies (e.g., ACTIVITY_TYPE_EXPORT_WALLET, ACTIVITY_TYPE_DELETE_AUTHENTICATORS).
• Fixes a missing \\ shell line continuation in the first curl call in exporting-wallet.mdx that would have caused the -H flags to be interpreted as a separate shell command.
• Regenerates the bundled openapi.yaml and mintlify/openapi.yaml via make build to reflect the source changes.

Confidence Score: 5/5

All changes are documentation and example values only — no functional code paths are touched.

Every changed line is an example payload, a header value in a curl snippet, or a shell line-continuation fix. The Turnkey activity JSON examples are internally consistent across MDX snippets and OpenAPI specs, the requestId format is uniformly updated to Request:, and the generated bundles match the source changes. The curl continuation fix in exporting-wallet.mdx corrects a real copy-paste failure that would have broken the example for readers.

No files require special attention.

Important Files Changed

Filename	Overview
mintlify/snippets/global-accounts/exporting-wallet.mdx	Fixed missing backslash line continuation in first curl call; updated payloadToSign and requestId examples to Turnkey format.
mintlify/snippets/global-accounts/authentication.mdx	Updated requestId format note, payloadToSign examples (EMAIL_OTP, PASSKEY) and Request-Id header values to use Request: and Turnkey activity payloads.
mintlify/snippets/global-accounts/managing-sessions.mdx	Updated payloadToSign and requestId examples for session revocation to use Turnkey ACTIVITY_TYPE_DELETE_API_KEYS format.
openapi/components/schemas/common/SignedRequestChallenge.yaml	Updated payloadToSign example from opaque base64 to generic Turnkey activity JSON placeholder.
openapi/paths/auth/auth_credentials.yaml	Updated payloadToSign examples for EMAIL_OTP, OAUTH, and PASSKEY credential challenges to canonical Turnkey activity payloads.
openapi/paths/customers/customers_{customerId}.yaml	Updated payloadToSign example for embedded wallet email update challenge to Turnkey ACTIVITY_TYPE_UPDATE_USER_EMAIL format.
openapi/paths/internal_accounts/internal_accounts_{id}.yaml	Updated payloadToSign example for internal account update challenge to ACTIVITY_TYPE_SIGN_RAW_PAYLOAD_V2 Turnkey format.
openapi.yaml	Generated bundle — identical diff to mintlify/openapi.yaml, correctly produced by make build from updated source files.
mintlify/openapi.yaml	Generated bundle — mirrors changes from openapi/ source files after make build.

Sequence Diagram

sequenceDiagram
    participant C as Client
    participant IB as Integrator Backend
    participant G as Grid API
    participant TK as Turnkey

    IB->>G: "POST /internal-accounts/{id}/export { clientPublicKey }"
    G-->>IB: "202 { payloadToSign (Turnkey JSON), requestId: Request:<uuid>, expiresAt }"
    IB-->>C: "{ payloadToSign, requestId }"
    C->>TK: stamp(payloadToSign, sessionPrivateKey)
    TK-->>C: base64url-encoded stamp
    C->>IB: "{ stamp }"
    IB->>G: "POST /internal-accounts/{id}/export { clientPublicKey } + Grid-Wallet-Signature + Request-Id"
    G-->>IB: "200 { id, encryptedWalletCredentials }"
    IB-->>C: "{ encryptedWalletCredentials }"
    C->>C: decrypt with client private key → mnemonic

Loading

_{Reviews (3): Last reviewed commit: "docs: update auth signed retry examples" | Re-trigger Greptile}

[github-actions]

✱ Stainless preview builds for grid

This PR will update the grid SDKs with the following commit messages.

cli

chore(internal): regenerate SDK with no functional changes

csharp

chore(tests): update PayloadToSign from base64 to JSON in auth credential tests

go

chore(internal): regenerate SDK with no functional changes

kotlin

chore(tests): update payloadToSign format in signed request challenge fixtures

openapi

docs(api): update payloadToSign examples across challenge responses

php

chore(internal): regenerate SDK with no functional changes

python

chore(internal): regenerate SDK with no functional changes

ruby

docs: update auth signed retry examples

typescript

chore(internal): regenerate SDK with no functional changes

Edit this comment to update them. They will appear in their respective SDK's changelogs.

✅ grid-openapi studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅

✅ grid-ruby studio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️ → build ⏭️ (prev: build ✅) → lint ⏭️ (prev: lint ❗) → test ⏭️ (prev: test ✅)

✅ grid-go studio · code · diff

Your SDK build had at least one "error" diagnostic, but this did not represent a regression.
generate ❗ → build ⏭️ (prev: build ✅) → lint ⏭️ (prev: lint ❗) → test ⏭️ (prev: test ❗)

go get github.com/stainless-sdks/grid-go@a7ea609e44f19b61adbc7e40385dd69b9d068f3e

✅ grid-kotlin studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅ → build ⏭️ (prev: build ✅) → lint ⏭️ (prev: lint ✅) → test ⏭️ (prev: test ✅)

✅ grid-python studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅ → build ⏭️ (prev: build ✅) → lint ⏭️ (prev: lint ✅) → test ⏭️ (prev: test ✅)

✅ grid-csharp studio · code · diff

Your SDK build had at least one "error" diagnostic, but this did not represent a regression.
generate ❗ → build ⏭️ (prev: build ❗) → lint ⏭️ (prev: lint ❗) → test ⏭️ (prev: test ❗)

✅ grid-php studio · code · diff

Your SDK build had at least one "error" diagnostic, but this did not represent a regression.
generate ❗ → lint ⏭️ (prev: lint ✅) → test ⏭️ (prev: test ✅)

✅ grid-cli studio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️ → build ⏭️ → lint ⏭️ → test ⏭️

✅ grid-typescript studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅ → build ⏭️ (prev: build ❗) → lint ⏭️ (prev: lint ❗) → test ⏭️ (prev: test ❗)

---

This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-05-19 20:40:20 UTC