---
title: "0xinsider API versioning and deprecation policy"
description: "Compatibility rules and deprecation guidance for the versioned 0xinsider Developer API."
canonical: "https://0xinsider.com/api-versioning"
last-updated: 2026-09-11
---

# 0xinsider API versioning and deprecation policy

## Current version

The public Developer API is versioned in its URL path. The current stable surface is /api/v1 at https://api.0xinsider.com. The discovery document and OpenAPI specification are the source of truth for the live operation list, parameters, schemas, and authentication requirements.

## Compatibility rules

- Additive fields, operations, and response metadata may be added to v1.
- Clients must ignore unknown JSON fields and follow the typed schemas for fields they use.
- A breaking change requires a new versioned path such as /api/v2; v1 is not silently repurposed for a breaking contract.
- The API origin's /api/v1/openapi.json endpoint remains a compatibility redirect to the canonical web-origin specification.

## Deprecation policy

Deprecated aliases are labeled in the OpenAPI operation description and in the agent reference. For example, /api/v1/markets/smart-money-flows remains live as a deprecated alias; new integrations should use /api/v1/markets/sharp-money-flows.

The current service documents deprecation in the OpenAPI specification, llms.txt, llms-full.txt, and this page. It does not currently promise Deprecation or Sunset response headers. Before removing a deprecated route, 0xinsider will publish the retirement date in the operation documentation and this policy page.

## Client guidance

Read https://0xinsider.com/api/v1 before selecting an endpoint, prefer canonical operation IDs over deprecated aliases, and refresh the OpenAPI document when an integration starts or when a response reports an unknown or deprecated operation.