docs.centrifuge.io APIdocs.centrifuge.io ↗
Query Centrifuge protocol pools, tokens, vaults, investor transactions, and positions. Plus full documentation search and page content extraction via 9 endpoints.
curl -X GET 'https://api.parse.bot/scraper/bb03b46f-ab3f-4de4-a249-1eda193ee1e3/get_page_content?url=https%3A%2F%2Fdocs.centrifuge.io%2Fuser%2Fconcepts%2Fpools%2F' \ -H 'X-API-Key: $PARSE_API_KEY'
Fetch the full content of any documentation page by URL. Returns title, full text, sections with headings and content, code blocks, and tables extracted from the page.
| Param | Type | Description |
|---|---|---|
| urlrequired | string | Full URL of the documentation page to fetch (e.g. 'https://docs.centrifuge.io/user/concepts/pools/') or a relative path (e.g. 'user/concepts/pools/'). |
{
"type": "object",
"fields": {
"url": "string, the resolved URL of the page",
"text": "string, full text content of the page",
"title": "string, page title from the h1 heading",
"tables": "array of arrays, each table as rows of cell text values",
"sections": "array of objects with level, title, id, and content for each heading section",
"code_blocks": "array of strings, text content of each code block on the page"
},
"sample": {
"data": {
"url": "https://docs.centrifuge.io/user/concepts/pools/",
"text": "Concepts\nPools\nOn this page\nPools\nA pool is the core structure...",
"title": "Pools",
"tables": [],
"sections": [
{
"id": "what-is-a-pool",
"level": "h2",
"title": "What is a pool?",
"content": "A pool brings together everything needed..."
}
],
"code_blocks": []
},
"status": "success"
}
}About the docs.centrifuge.io API
This API exposes 9 endpoints covering both the Centrifuge documentation site and the Centrifuge on-chain protocol data. You can retrieve full documentation page content, search across docs via search_documentation, navigate the site hierarchy, and query live protocol data — including pools, share class tokens, ERC-4626 vaults, investor transactions, and token positions — directly through typed GraphQL endpoints or a freeform graphql_query endpoint.
Documentation Endpoints
The get_page_content endpoint accepts a full or relative URL from the docs.centrifuge.io domain and returns the page title, full text, structured sections (each with level, title, id, and content), extracted tables as row arrays, and code_blocks. This makes it straightforward to pull specific concept pages, integration guides, or reference material programmatically. The get_site_navigation endpoint returns both a nested navigation tree and a flat all_urls list covering every page in the documentation site. search_documentation runs a full-text search and returns hits containing url, content snippets, and hierarchy breadcrumbs useful for contextual lookup.
Protocol Data Endpoints
Five typed GraphQL convenience endpoints cover the main Centrifuge protocol objects. graphql_query_pools returns each pool's id, name, centrifugeId, isActive flag, and associated share class tokens. graphql_query_tokens adds token-level detail: symbol, totalIssuance, tokenPrice, and the underlying pool asset decimals. graphql_query_vaults exposes vault deployment details including assetAddress, poolId, tokenId, status, and blockchain context. All three support limit and offset for pagination.
Investor Data and Custom Queries
graphql_query_investor_transactions returns transaction records with txHash, type, account, poolId, tokenAmount, currencyAmount, and createdAt. It accepts an optional account parameter (Ethereum address) to filter to a specific investor. graphql_query_investor_positions similarly accepts an account filter and returns tokenId, accountAddress, balance, isFrozen, and the token contract address. For queries beyond these prebuilt endpoints, graphql_query accepts an arbitrary GraphQL query string plus a JSON variables string — named operation syntax is required when passing variables.
- Monitor active Centrifuge pools and their share class tokens by polling
graphql_query_poolsforisActivestatus changes. - Build an investor dashboard by querying
graphql_query_investor_transactionsandgraphql_query_investor_positionsfiltered by Ethereum account address. - Index the full Centrifuge documentation site for an internal knowledge base using
get_site_navigationto enumerate URLs thenget_page_contentto extract text and sections. - Surface relevant Centrifuge protocol concepts in a developer tool by running
search_documentationqueries and returning ranked content snippets. - Track vault deployment status across blockchains by polling
graphql_query_vaultsforstatusandisActivechanges perpoolId. - Fetch token price and total issuance data for Centrifuge share classes via
graphql_query_tokensfor yield or NAV calculations. - Run ad-hoc protocol analytics by sending custom GraphQL queries through
graphql_querywith structuredvariables.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Centrifuge have an official developer API?+
What does `graphql_query_investor_transactions` return and how do I filter by investor?+
txHash, type, account, poolId, tokenAmount, currencyAmount, and createdAt. Pass an Ethereum address as the optional account parameter to filter results to a single investor's activity.Does `graphql_query_vaults` return historical vault state or only current status?+
status and isActive flag at query time. Historical vault state changes are not exposed through this endpoint. You can fork the API on Parse and revise it to add a time-series or event-log endpoint if historical state tracking is needed.Can I retrieve pool NAV or loan-level asset data through the pool endpoints?+
graphql_query_pools returns pool identity fields (id, name, centrifugeId, isActive) and token associations, not NAV calculations or individual loan records. You can fork the API on Parse and revise it to add a custom graphql_query call that targets loan or NAV fields from the Centrifuge protocol GraphQL schema.Are there pagination controls on the protocol data endpoints?+
limit and offset integer parameters. The investor transaction and position endpoints accept limit but not offset — use the account filter to narrow results rather than paginating through a full dataset.