Migrating from API v1 to v2
Esta página aún no está disponible en tu idioma.
This guide helps you migrate from API v1 to v2.
Breaking Changes
Section titled “Breaking Changes”Base URL Change
Section titled “Base URL Change”https://api.acme.com/v1https://api.acme.com/v2User Object Changes
Section titled “User Object Changes”{ "id": "usr_abc123", "user_email": "alice@example.com", "email": "alice@example.com", "user_name": "Alice Smith", "name": "Alice Smith", "created": "2024-01-10", "created_at": "2024-01-10T08:00:00Z", "status": "active"}Pagination Changes
Section titled “Pagination Changes”v1 (offset-based):
{ "users": [...], "total": 150, "page": 1, "per_page": 20}v2 (cursor-based):
{ "data": [...], "has_more": true, "next_cursor": "cur_xyz789"}Authentication Header
Section titled “Authentication Header”X-API-Key: sk_live_abc123Authorization: Bearer sk_live_abc123Migration Checklist
Section titled “Migration Checklist”- Update base URL to
/v2 - Update authentication header format
- Update field names in request/response handling
- Switch from offset to cursor-based pagination
- Update error handling for new error format
- Test all API integrations thoroughly
Deprecation Timeline
Section titled “Deprecation Timeline”| Date | Action |
|---|---|
| June 1, 2024 | v1 deprecation announced |
| September 1, 2024 | v1 returns deprecation warnings |
| December 31, 2024 | v1 endpoints disabled |
Need Help?
Section titled “Need Help?”Contact support@acme.com for migration assistance.