Skip to main content
All API endpoints follow the structure — https://api.messari.io/<slug>/v1/<endpoint>
<slug> represents the specific service being accessed (e.g., marketdata, ai, news, etc.)/v1/ denotes the API version<endpoint> refers to the specific resource or operation being requested
Versioning Strategy
Messari adheres to a semantic versioning approach for API updates:
- Breaking Changes: Any changes that alter existing functionality in a non-backward-compatible way will result in a version bump (e.g., from
v1 to v2).
- Non-Breaking Changes: Additions such as new endpoints, optional parameters, or enhancements to existing functionality will be introduced within the current version (
v1).
Deprecation and Change Management
- Older versions of the API will remain accessible for a defined period after a new version is introduced.
- Deprecation notices will be provided in advance, along with migration guides.
- All changes, including enhancements and deprecations, will be documented in the API Changelog.
