Choose your API version
Usehttps://api.remapdb.com/v2 for new REST integrations. Existing integrations can continue using https://api.remapdb.com/v1 during the migration period. The same Bearer API key works with both versions, and both share your existing request allowance.
V1 retains the shared-catalog behavior. Enabling Customizations in your account does not change v1 responses. V2 uses your customized catalog when your subscription includes Customizations; otherwise it returns the shared catalog using the v2 response contract.
The hosted MCP endpoint, widgets, and WordPress integration use the updated catalog directly. Their URLs are unchanged.
Update your client before switching URLs
Changing only the base URL may break an older generated client. Regenerate or update it against the v2 OpenAPI specification, then test representative list, detail, search, and chart responses.
Migration checklist
- Update your field types, stage keys, nullable assets, and cache scope.
- Test v2 using your existing API key, including any customized or hidden records.
- Compare your rendered results and pagination with your current integration.
- Switch your integration to
/v2and clear its v1 response cache. - Monitor errors and missing records. While v1 remains supported, reverting the URL restores the legacy contract.
Deprecation and retirement
V1 support is planned for approximately three months after the v2 launch. The exact retirement date will be announced at launch; no date is fixed by this guide. V1 responses link to this guide. Once configured at launch,Deprecation identifies the deprecation date and Sunset identifies the announced retirement date. These headers do not change the response body or automatically stop requests.
Retirement will happen in a separate release. Retired v1 endpoints will return 410 Gone with migration guidance, rather than silently redirecting requests to v2. The v1 specification and existing reference pages remain available during the transition.