Use this section when
- You want to pull Remapdb data into your own backend.
- You want to automate workflows outside the Remapdb interface.
- You want to connect AI tools to Remapdb vehicle tuning data through API access.
- You need a clear setup path for credentials, endpoint usage, and daily request planning.
API access depends on your plan and feature access.
What you can do from the API page
- Copy your
API keyandAPI secret. - Click the Generate new credentials button when you need to rotate keys.
- Click the API documentation link for endpoint contracts.
- Open API reference for interactive endpoint docs.
- Use API access with MCP-based AI tools through AI Integrations.
- Click the PHP SDK or JavaScript SDK link if you prefer SDK-based integration.
Recommended order
- Start with Credentials and authentication.
- Connect Remapdb AI Integrations if you want MCP-based AI tools to use vehicle data through API access.
- Continue with Best practices before go-live.
- Check Usage limits so traffic stays stable.
- If credentials are locked, open Plan access.
Success looks like
- Your integration authenticates successfully.
- Your requests return expected data in staging and production.
- You can monitor usage and rotate credentials without downtime.
Pages in this section
Credentials and authentication
Copy, store, and rotate API credentials safely.
AI Integrations
Use API access to connect MCP-based AI tools to Remapdb vehicle tuning data.
Best practices
Use security, reliability, and rollout standards that prevent outages.
Plan access
Check which plans include API access and unlock credentials if needed.
Usage limits
Plan daily request volume and avoid limit-related interruptions.
API reference
Browse interactive endpoint documentation.