Skip to main content
Use this page to connect your backend to Remapdb with a safe credential workflow.

​
Where to find credentials

Click the API item in the main navigation. In the Credentials section, you will see:
  • API key
  • API secret
  • Copy buttons
  • Generate new credentials button
If credentials are disabled, your account does not currently have API access. Open Plan access.

​
Set up credentials

1

Copy both credential values

Click the Copy button next to API key, then click the Copy button next to API secret.
2

Store credentials in your server environment

Save both values in secure server-side environment variables or your secret manager.
3

Connect your backend service

Configure your backend to read the stored credentials and use them for API requests.
4

Run one test request in staging

Confirm authentication works in staging before you send production traffic.
Your API key is also used for MCP-based AI tool setup. Set it as REMAPDB_API_KEY when you follow AI Integrations.

​
Rotate credentials safely

Clicking the Generate new credentials button creates a new key and secret pair.
Rotation is immediate. As soon as you generate new credentials, old credentials stop working.
Use this rotation order:
1

List every service that uses current credentials

Include web app backend, workers, scheduled jobs, and any integration scripts.
2

Generate the new credentials in Remapdb

Click the Generate new credentials button in the API page.
3

Update credentials in every environment

Replace old values in staging and production secret storage.
4

Reload services

Restart or redeploy services so they read the new values.
5

Run a smoke test

Confirm your key requests succeed and no authentication errors appear in logs.

​
Common issues

  • Credentials are disabled: open Plan access.
  • Requests started failing right after rotation: one or more services still use old credentials.
  • Staging works but production fails: compare environment variables between both environments.