Developer access
One key.
Two APIs.
Connect your tools to tuning files and diagnostic evidence with your RedlineAutohaus account.
Submit evidence from the start.
Every active key can submit UDS logs and read its submission status. Your account gets its own private workspace automatically. Approval and publication remain reserved for explicitly authorized administrators.
- Sign in and verify your email.
- Open Account → Settings → API access, name your key and select any additional permissions.
- Confirm your password and save the key. Its full value appears once.
- Send it in the Authorization header to either API.
curl https://api.redlineautohaus.com/api/v1/uds/capabilities \
-H "Authorization: Bearer $REDLINE_API_KEY"Keep the key in your application's secret storage. Do not include browser cookies with it.
Choose what your integration can do.
| Product | Access |
|---|---|
| UDS evidence | Included: submit logs and read your records. Optional permissions unlock sensitive evidence and original artifacts. |
| Tuning files | Select read, upload, download and credit-spending permissions. Downloads retain the account's existing access and prices. |
| Trusted protocols | Read deliberately published knowledge. Approval, revisions, redactions and publication require explicit administrative access. |
API keys do not provide access to staff-only file management, internal verification workers or unrelated AutoClever and MCP tools.
Build and maintain your integration.
- Full guide: curl, JavaScript and Python examples, uploads, quotas and errors
- Tuning API reference
- UDS API reference
Rotate or revoke keys from account settings. Password changes and resets revoke all existing keys. Administration → API access controls account limits and privileged UDS capabilities without interrupting ordinary evidence submission.