Cost: 1 credit per call (WALLET credits)
Interactive Playground: Test this endpoint in the API Playground. Get your API key at data.octav.fi
Endpoint
Path Parameters
Chain identifierSupported chains:
arbitrum, avalanche, base, binance, ethereum, fantom, gnosis, linea, optimism, polygonSee Supported Blockchains for detailsRequired Parameters
Wallet address to fetch approvals for
Optional Parameters
Number of results per page
- Minimum: 1
- Maximum: 100
- Default: 25
Cursor string from a previous response to fetch the next page
Response
Top-Level Fields
Cursor for the next page.
null or absent when there are no more results.Number of items returned in this page.
Array of token approval records.
Approval Object
Each item initems contains:
Block number where the approval transaction was mined.
ISO 8601 timestamp of the block.
Transaction hash of the approval.
Address of the token contract that was approved.
Wallet address that granted the approval.
Spender address that received the approval.
Raw approved amount (not decimal-adjusted). A max
uint256 value indicates unlimited approval.Enriched token metadata. Present only when the token is tracked in the Octav asset database.Contains:
name, symbol, balance, price, value, decimal, chain, contract, imgSmall, imgLargeFollows the standard AssetViewModel shape used across other Octav API responses.Example Request
Example Response
View Full Response
View Full Response
Pagination
Use cursor-based pagination to iterate through results:- Make an initial request with just
limit(or use the default of 25) - If the response contains a non-null
cursor, pass it as thecursorquery parameter in the next request - When
cursorisnullor absent, you have reached the end of the results
Use Cases
- Audit Approvals
- Multi-Chain Overview
- Track Approval Value
- Spender Analysis
Review all active token approvals for security:
Error Responses
400 Bad Request
400 Bad Request
Invalid parameters provided.Common causes:
- Invalid or unsupported chain in URL path
- Missing
addressesquery parameter limitout of range (must be 1-100)
402 Payment Required
402 Payment Required
502 Bad Gateway
502 Bad Gateway
Upstream data provider is unavailable.Solution: Retry after a short delay. If the issue persists, the upstream provider may be experiencing an outage.
Related Endpoints
Portfolio
View current portfolio holdings
Transactions
Query full transaction history
Wallet
Get wallet balances across protocols
Token Overview
Detailed token breakdown by protocol