Moving from nblocks to The Bridge
If you are migrating from nblocks to The Bridge, the only change you need to make is to update your API base URLs. Request and response shapes, authentication (API key and headers), and behavior are the same.
Endpoint mapping
Section titled “Endpoint mapping”Replace the base URL in all your API calls according to this table:
| Previous (nblocks) | The Bridge |
|---|---|
https://account-api.nebulr-core.com | https://api.thebridge.dev/account |
https://auth.nblocks.cloud | https://api.thebridge.dev/auth |
https://backendless.nblocks.cloud | https://api.thebridge.dev/cloud-views |
https://communication-api.nebulr-core.com | https://api.thebridge.dev/communication |
https://admin-api.nblocks.cloud | https://api.thebridge.dev/admin |
What stays the same
Section titled “What stays the same”- Authentication — Use the same
x-api-key(andx-tenant-idwhere applicable) headers. - Request bodies and query parameters — No changes to payloads or query strings.
- Response formats — JSON responses have the same structure.
- HTTP methods and paths — Only the host (base URL) changes; path segments are unchanged.
Example
Section titled “Example”Before (nblocks):
curl --request GET 'https://account-api.nebulr-core.com/tenant' \ --header 'x-api-key: YOUR_APP_API_KEY'After (The Bridge):
curl --request GET 'https://api.thebridge.dev/account/tenant' \ --header 'x-api-key: YOUR_APP_API_KEY'Update every occurrence of the old base URLs in your codebase (client code, config, or environment variables) to the new base URLs above, and you’re done.