General Information
Domains
The CardanoBI API
is organized by domains.
There are currently 3 domains:
- Core
- BI
- Partner
Core is the fundamental domain where all on-chain entities and interactions live.
BI is an enhanced domain on top of Core, this domain integrates and aggregates data from Core, enabling comprehensive analytics and insights for informed decision-making.
Partner is a specialized domain, dedicated to the integration of third-party data, either on-chain or off-chain, expanding the scope of available data and enhancing the depth and breadth of business analytics and intelligence.
Environments
CardanoBI
supports 3 Cardano environments:
- Mainnet
- Preprod
- Preview
This is the live
environment where real business interactions happen.
This is a replica of the mainnet
environment in its parameters (epoch duration, etc...).
This is the environment where non-regression tests are carried out before mainnet release.
This is a lighter environment with much shorter epochs (1 day). It is geared towards iterative and incremental development with short feedback loop.
Base Endpoints
CardanoBI
base endpoints are Cardano environment specific.
- Mainnet
- Preprod
- Preview
Responses
All responses are JSON objects or arrays of JSON objects.
Data is returned in ascending order (oldest first, newest last).
HTTP Return Codes
- 200
- 400
- 401
- 402
- 403
- 404
- 429
OK: Successful request.
Bad Request: The request was unacceptable, often due to missing a required parameter.
Unauthorized: No valid API key provided.
Quota Exceeded: This API key has reached its usage limit on request.
Access Denied: The request is missing a valid API key or token.
Not Found: The requested resource cannot be found.
Too Many Requests: This API key has reached its rate limit.
Pagination
By default the number of records in the response will be limited to 20.
Some endpoints allow to increase this up to 100.
Please refer to the API Documentation of individual endpoints for further information.
- page_size : integer [1 - 100] : will set the maximum page size of the response
- page_no : integer [>0] : will set the page number of the response
- order : string : 'asc' (default) will order the records in ascending order, 'desc' will order the records in descending order
ODATA Query Options
All endpoints support $select, $filter, $orderby, $count query options.
More information on how to use them can be found here.