Migration guide (v1 → v2) v1 retired
v1 reached end of life on 2026-08-01 alongside the webhooks GA changelog entry. This guide covers the three breaking changes you need to handle to move a v1 integration to v2.
1. Pagination: offset → cursor
v1 used page/per_page query parameters. v2 uses an opaque cursor and next_cursor — see Rate limits for the exact envelope.
- GET /v1/pipelines?page=2&per_page=20
+ GET /v2/pipelines?cursor=eyJvZmZzZXQiOjIwfQ2. Status checks: polling → webhooks
v1 had no push notifications — you polled a pipeline's status endpoint. v2 replaces this with the Webhooks endpoint: subscribe to pipeline.completed and pipeline.failed instead of polling.
3. Error shape
v1 returned bare error strings. v2 wraps every error in an object with a stable code field. Update any error handling that matched on message text — see the error shape reference.
v1 endpoints no longer accept requests. If you're seeing 404s on /v1/* paths, that's why — there is no grace-period fallback.
Still stuck?
Support / Contact
Before reaching out, check Troubleshooting / FAQ — most common issues are covered there.
Channels
- Technical support: support@kmp.kaiju.go.example
- Sales: sales@kmp.kaiju.go.example
- Security reports: security@kmp.kaiju.go.example — see Security & compliance overview for our disclosure policy.
Standard-tier support responds within one business day. Include your workspace ID and, if relevant, a request_id from an error response.
Common migration issues are covered in Troubleshooting / FAQ.