Versioning

The Inspow API uses URL versioning (URI versioning). The version is included in the path of each request, which lets you migrate at your own pace when breaking changes are released.

Version scheme

All routes share the api prefix followed by the version:

https://api.inspow.tech/api/v1/<resource>

The default version is 1. If you omit the version in a request, the default version is resolved, but we recommend always stating it explicitly to avoid surprises in the future.

Version	Base path	Status
v1	/api/v1	Stable

Tip

In the API Reference section of the sidebar, all routes are written starting from /api/v1.

Unversioned endpoints

Some endpoints are version-neutral: they don’t carry a version number in the path, because they are called by external systems with a URL configured in advance and must stay stable even if the API version changes:

Endpoint	Path	Use
Health	/api/health (and /api/health/ready, /api/health/live)	Service status check.
Payment webhooks	/api/payments/<gateway>/webhook	Events from the payment gateway (see Webhooks).
WhatsApp webhook	/api/wa/webhook	Meta events for the WhatsApp agent.
Integration webhooks	/api/integrations/webhooks/...	Events from connected accounting systems.

Caution

Don’t prefix these endpoints with v1. For example, use /api/health, not /api/v1/health.

Note

When there is a new version, we’ll announce it in this documentation together with the changes and the migration deadline. Today the only version is v1.