The /v1/export API endpoint is now officially deprecated and will be removed on April 1, 2026.
If your integration calls /v1/export, you have approximately 10 weeks to migrate to /v2/specs. The v2 API is stable, fully documented, and has been in production since v2.0.0.
What’s changing
The /v1/export endpoint was introduced in the early beta and returns a flat JSON object. The /v2/specs endpoint returns a richer, versioned response envelope and supports filtering, pagination, and webhook event correlation.
| Feature | /v1/export | /v2/specs |
|---|---|---|
| Response envelope | Flat | Versioned data + meta |
| Pagination | No | Cursor-based |
| Webhook correlation | No | Yes (specId matches) |
| Token scopes | Any | Granular |
| Deprecation date | Apr 1, 2026 | — |
Migration
Replace calls to POST /v1/export with GET /v2/specs/{specId}. Full migration guide is in the API docs.
The response shape for /v2/specs wraps content under data:
GET /v2/specs/sp_01HZ7QX2Y
Authorization: Bearer ink_live_...
{
"data": {
"id": "sp_01HZ7QX2Y",
"title": "Homepage redesign",
"exportedAt": "2026-01-20T10:00:00Z",
"frames": [...]
},
"meta": { "version": "2" }
}
After April 1, calls to /v1/export will return 410 Gone. To request an extension, contact support.