Migrating from an incumbent screening API
One day, three environment variables, nothing else.
What actually changes
Your worker's request construction, token computation, form encoding and field names stay untouched. Only the base URL and your issued credential change — repoint three environment variables and the same code keeps working.
| Variable | Repoint to |
|---|---|
AMLBOT_URL | Your compat endpoint host (issued with your tenant) |
AMLBOT_ID | Your compat credential's accessId |
AMLBOT_KEY | The same compat credential's secret |
What stays identical
Every field name and shape in the response body is reproduced exactly, including the pending-status poll loop your worker already implements.
What is better once you have time to switch
Our own API surface gives every finding a real, dereferenceable source link instead of an unlinked category label — worth switching to directly once the compatible endpoint has bought you time.
What is not available yet, stated plainly
The signed PDF evidence-report field is null until that feature ships in a later release — this is disclosed rather than silently omitted, and it holds regardless of which provider serves the request.