Migration to api.capturia.io

The Capturia public API is now served on its dedicated subdomain. Migrate before May 3, 2027 to avoid automatic redirection.

Before / After

curl example

# Before
curl https://app.capturia.io/api/v1/me \
  -H "Authorization: Bearer cap_live_xxx"

# After
curl https://api.capturia.io/v1/me \
  -H "Authorization: Bearer cap_live_xxx"

Make / Zapier

In the HTTP module, change the URL from https://app.capturia.io/api/v1/... to https://api.capturia.io/v1/.... No other change required — the API key and request format remain identical.

What happens if I don't migrate before 2027-05-03?

Your requests on the legacy host will automatically receive HTTP 308 Permanent Redirect to the new host with the same path. Most HTTP clients (curl, axios, fetch, Python requests, Make, Zapier) follow redirects by default — your integration will continue working without code changes, with a small network overhead of one round-trip. To eliminate this overhead, update the URL in your code.

If your HTTP client doesn't follow redirects, it will receive the 308 status with a JSON body explaining the migration. Your code will then need adaptation.

Signaling headers (before sunset)

All responses on the legacy host carry these IETF headers:

• Deprecation: true (RFC 9745)
• Sunset: Sun, 03 May 2027 00:00:00 GMT (RFC 8594)
• Link: <https://api.capturia.io>; rel="successor-version" (RFC 8288)
• Capturia-Migration-Notice — human-readable message

OpenAPI bundle

The OpenAPI 3.1 spec is now served at the canonical address: https://api.capturia.io/openapi.yaml (or .json). Postman/Insomnia/Stoplight auto-discovery from this URL.