Skip to content

docs: sync api reference 2026-06-22#96

Open
JamesLawton wants to merge 2 commits into
mainfrom
docs/update-api-reference-2026-06-22
Open

docs: sync api reference 2026-06-22#96
JamesLawton wants to merge 2 commits into
mainfrom
docs/update-api-reference-2026-06-22

Conversation

@JamesLawton

Copy link
Copy Markdown
Collaborator

What changed

Two narrowly-scoped API additions landed in trails-api release this week and are missing from the docs OpenAPI specs.

  • Intent.timedRefundUnlockTimestamp — new optional number field on the Intent schema. Unix timestamp (in seconds) after which the timed-refund sapient signer can execute refunds for an intent's wallets. Only set when timed refund support was enabled at quote time (v1.5 intents). Added to:

    • api-reference/trails-api.gen.yaml
    • api-reference/trails-api.gen.json
    • api-reference/before-annotations-trails-api.gen.json
  • ErrorIntentProtocolDeprecated — new error schema (code 3000, HTTP 422). Returned when the requested intent protocol version is outdated/deprecated and the client must upgrade the Trails SDK. Added as a schema definition next to the other Error* schemas in the three spec files above.

The error response is wired into 40+ endpoint responses upstream; this PR adds only the schema definition. Wiring the oneOf references into each endpoint can be done in a follow-up sync.

Source of truth

  • trails-api PR #892 — Add timed refund leaf to 1.5 intents (commit 5658e33) — introduced Intent.timedRefundUnlockTimestamp in proto/trails-types.ridl.
  • trails-api proto/trails-api.ridl line 709: error 3000 IntentProtocolDeprecated "..." HTTP 422.
  • Generated OpenAPI: trails-api proto/docs/trails-api.gen.yaml at commit 103d6ba (current release HEAD).

Verification

  • Confirmed TimedRefundUnlockTimestamp ships with json:"timedRefundUnlockTimestamp,omitempty" in proto/trails-api.gen.go, so it is part of the wire response (unlike statusUpdatedAt/eligibleAt on IntentTransaction, which are tagged json:"-" and therefore intentionally omitted from these docs).
  • Schema changes match the upstream YAML at trails-api/proto/docs/trails-api.gen.yaml lines 1410-1411 (timedRefundUnlockTimestamp) and 803-824 (ErrorIntentProtocolDeprecated).
  • No MDX page references either symbol, so existing pages render unchanged; the new field/error appear in any auto-generated schema views.

Generated by the Trails Docs weekly agent.


Generated by Claude Code

claude added 2 commits June 22, 2026 09:11
Sync two API-visible additions landed in trails-api this week:

- Intent.timedRefundUnlockTimestamp (optional uint64) - unix timestamp
  after which the timed-refund sapient signer can execute refunds for
  the intent's wallets. Set only when timed refund support was enabled
  at quote time. Backs the v1.5 timed-refund leaf in trails-api #892.

- ErrorIntentProtocolDeprecated (code 3000, HTTP 422) - returned when
  the requested intent protocol version is outdated. Added in
  trails-api proto/trails-api.ridl.

Updates trails-api.gen.yaml, trails-api.gen.json, and
before-annotations-trails-api.gen.json.
pnpm v8 (pinned in .github/workflows/convert-openapi.yml) rejects a
workspace yaml that lacks a packages field with
ERR_PNPM_INVALID_WORKSPACE_CONFIGURATION. The Convert OpenAPI workflow
fires on changes to api-reference/trails-api.gen.yaml, so this surfaces
only when the YAML is edited - which hadn't happened since #88
introduced the workspace file.

Adding packages: [] preserves the intent of using the file purely for
minimumReleaseAge / allowBuilds settings while satisfying pnpm 8's
schema validation.
@mintlify

mintlify Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
trails 🟢 Ready View Preview Jun 22, 2026, 9:20 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants