Skip to content

Conversation

@shaneauerbach
Copy link
Collaborator

Summary

  • Adds Warning schema and warnings field to the OpenAPI specs for Token Info, Collectibles, and DeFi Positions endpoints
  • Extends the unsupported chain ID warnings (introduced in Chain id warnings infrastructure #136 for Balances) to all EVM endpoints for consistency
  • When users request data for unsupported chain IDs, responses now include a warnings array with helpful information

Changes

The following OpenAPI specs were updated:

  • evm/openapi/token-info.json - Added Warning schema and warnings field to TokensResponse
  • evm/openapi/collectibles.json - Added Warning schema and warnings field to CollectiblesResponse
  • evm/openapi/defi-positions.json - Added Warning schema and warnings field to DefiPositionsResponse

Warning Structure

{
  "warnings": [
    {
      "code": "UNSUPPORTED_CHAIN_IDS",
      "message": "Some chain_ids are not supported.",
      "chain_ids": [9999, 77777777777],
      "docs_url": "https://docs.sim.dune.com/evm/supported-chains"
    }
  ]
}

Related

Test plan

  • Verify OpenAPI specs are valid JSON
  • Verify warning schema matches the Balances endpoint pattern
  • Review rendered documentation in Mintlify preview

…dpoints

Extends the unsupported chain ID warnings (introduced in #136 for balances)
to the remaining EVM endpoints. When users request data for unsupported
chain IDs, the API now returns a warnings array with:
- code: UNSUPPORTED_CHAIN_IDS
- message: Human-readable description
- chain_ids: List of unsupported chain IDs
- docs_url: Link to supported chains documentation

This provides consistent behavior across all EVM endpoints.
@cursor
Copy link

cursor bot commented Jan 16, 2026

PR Summary

Introduces non-fatal warning support across key EVM endpoints.

  • Adds reusable Warning schema (code, message, optional chain_ids, docs_url)
  • Adds warnings array to TokensResponse, CollectiblesResponse, and DefiPositionsResponse

Written by Cursor Bugbot for commit 4855ce3. Configure here.

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