Skip to content

chore: update openapi specs for deficarrot,defituna lulo,marginfi#46

Open
github-actions[bot] wants to merge 1 commit intomainfrom
chore/sync-openapi-specs
Open

chore: update openapi specs for deficarrot,defituna lulo,marginfi#46
github-actions[bot] wants to merge 1 commit intomainfrom
chore/sync-openapi-specs

Conversation

@github-actions
Copy link

Automated daily sync of OpenAPI specs from live APIs.

Review the diff and merge when ready — Mintlify will rebuild automatically.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spec changes

1. New endpoints

No new endpoint paths or HTTP methods were added across the updated specs:

  • openapi/deficarrot.json
  • openapi/defituna.json
  • openapi/lulo.json
  • openapi/marginfi.json

2. Deprecated or removed fields/endpoints

No deprecated: true flags were added or removed, and no endpoints were removed.

Removed fields/examples observed:

  • deficarrot: removed request body named examples for mint/redeem POST responses.
  • deficarrot + marginfi: removed some parameter schema.examples arrays in favor of example/default usage.
  • defituna: removed empty components.schemas block (structural cleanup only).
  • defituna + marginfi: replaced schema.x-example with standard schema.example.

3. New or modified parameters (required vs optional)

No required/optional flag changes were detected for parameters.

Modified parameters:

  • deficarrot (/v0/crt/mint/{poolToken}, /v0/crt/redeem/{poolToken}):
    • poolToken default/example changed from USDC to PYUSD on POST endpoints, and default/example now explicitly present on GET endpoints.
  • defituna (/v0/lend/{poolToken}/deposit|withdraw):
    • parameter examples normalized to standard example.
    • percentage metadata now includes explicit x-default and example on POST endpoints.
  • marginfi (/v0/lend/{tokenSymbol}/deposit|withdraw POST):
    • parameter serialization metadata changed (style/explode removed, allowEmptyValue/allowReserved added).
    • added/normalized example + x-default on percentage-like params.

4. Schema/type changes

Most significant behavioral schema changes are in defituna:

  • GET responses (deposit + withdraw):
    • links.actions[].type changed from a fixed const: "transaction" to enum: ["transaction", "external-link"].
  • POST responses (deposit + withdraw):
    • added links.next object shape (type, href) and dialectExperimental.reference fields.

Additional structural metadata changes:

  • operation IDs are now protocol-namespaced in all 4 specs (e.g., defituna.v0..., marginfi.v0..., etc.).
  • x-mint.href was added on operations to pin API reference routes.

5. Description updates

  • deficarrot operation summaries were simplified:
    • Get mint blink -> Mint
    • Mint operation -> Mint
    • Get redeem blink -> Redeem
    • Redeem operation -> Redeem
  • defituna info title changed:
    • DeFiTuna Blinks -> Defituna Blinks API

Documentation that may now be outdated

I searched .mdx files for changed identifiers/paths and found the following likely review targets.

  1. API reference link targets likely stale after route namespacing (x-mint.href additions)
  • release-notes/index.mdx
  • This file still references legacy paths like /api-reference/mint/get-mint-blink and /api-reference/lend/lend-deposit, while specs now explicitly annotate namespaced routes such as:
    • api-reference/deficarrot/earn/mint-get
    • api-reference/defituna/lend/deposit-get
    • api-reference/lulo/deposit/deposit-get
    • api-reference/marginfi/lend/deposit-get
  1. Client integration docs that currently model action buttons as transaction-only
  • standard-blinks-library/quick-start.mdx
  • blinks/blinks-client/integrate/headless/index.mdx
  • Both heavily show links.actions[].type: "transaction" and do not clearly call out the new external-link possibility now present in updated DeFiTuna GET response schema.
  1. Chaining/response-shape docs to validate against new POST response shape
  • standard-blinks-library/quick-start.mdx
  • blinks/blinks-client/integrate/headless/index.mdx
  • blinks/blinks-provider/advanced/action-chaining.mdx
  • DeFiTuna POST responses now include links.next + dialectExperimental fields; worth aligning consumer-oriented examples and expectations.

Deprecations (high priority)

No explicit deprecations were introduced in this PR:

  • no new deprecated endpoints
  • no newly deprecated fields
  • no removals marked as deprecation migrations

High-priority note anyway: because links.actions[].type expanded (transaction + external-link), consumer assumptions may break even without formal deprecations.

Suggested action items for DevRel

  1. Validate and update stale API reference links in release-notes/index.mdx to current namespaced routes emitted by x-mint.href.
  2. Update client-facing integration docs (standard-blinks-library/quick-start.mdx, blinks/blinks-client/integrate/headless/index.mdx) to explicitly handle links.actions[].type = "external-link".
  3. Add a short compatibility note/changelog callout that some protocol GET action schemas are no longer transaction-only.
  4. Add a note in protocol docs that DeFiCarrot poolToken default shifted to PYUSD (important for copy/paste tests and examples).
  5. Re-test code examples that parse POST responses as only { type, transaction } and ensure they tolerate optional links.next/dialectExperimental additions.
Open in Web View Automation 

Sent by Cursor Automation: PR Summary Bot

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

Development

Successfully merging this pull request may close these issues.

1 participant