Skip to main content

Coinbase Cloud API Versioning

All Coinbase Cloud APIs use semantic versioning to ensure compatibility.

The version is specified after the service, as in /eth2/v1. Only the major version is used to determine and enforce semantic version compliance. The implication of this approach is that existing clients will continue to work as the API evolves with features and fixes, and will only need to be modified when a new major version is released. Major versions are, by semantic versioning convention, not backwards compatible.

Was this helpful?