API Versioning and Deprecation Policy

How DataLikers versions its API, how an endpoint is deprecated, and what happens when it is removed.

Versioning

• The version is part of the path: /v1 and /v2 for Instagram, /t1 for TikTok. A newer version of an endpoint is added next to the old one, and the old one keeps working until it is deprecated and removed under this policy.
• Additive changes ship without notice: new endpoints, new optional parameters, new fields in responses. Clients should ignore response fields they do not recognize.
• An existing endpoint never changes in a breaking way in place. A breaking change ships as a new endpoint or a new version.

Why endpoints are deprecated

DataLikers returns public Instagram and TikTok data. Most deprecations start on the platform's side: the platform changes or removes the data an endpoint relies on. Less often, we replace an endpoint with a better one ourselves.

How a deprecation is announced

• The endpoint is marked deprecated in the OpenAPI spec, so the interactive docs at api.datalikers.com/docs show it as deprecated.
• The changelog names the deprecated endpoint and the one to use instead.

How long a deprecated endpoint keeps working

• Our own replacements: at least 90 days between the announcement and removal.
• Changes on the platform's side: we keep the endpoint working for as long as the platform allows. There is no guaranteed window: between the first warning and a full block it can be anything from a week to several months, and the platform can cut an endpoint off sooner. We announce it as soon as we know.

After removal

A removed endpoint answers 410 Gone with a JSON error that names its replacement. Requests that get a 410 are not billed.

Questions

If you depend on an endpoint that is being deprecated, contact support — we will help you move to the replacement.