What the diagnostic token is for
A diagnostic token is used by supported ISTA security workflows to authorize a specific protected operation. The token is created from a request that contains the context required by the upstream service.
Tokens are not general-purpose license files. They may depend on the vehicle, request content, diagnostic context and time or session constraints.
Creating the request file
- Generate the request in the local ISTA-compatible process for the exact operation you plan to complete.
- Save the exported request without editing its payload. Keep a note of the vehicle and workflow stage associated with it.
- If the local process offers different request modes, use the mode that matches the generated file. Do not enable an alternative/raw mode only as a troubleshooting guess.
Submitting online
- Sign in, open the ISTA Diagnostic Token page and select the request file.
- Confirm the mode, submit the request and wait for the backend response. Keep the page open until the result or a clear error is displayed.
- After successful preparation, download the result and return to the same ISTA workflow.
Why a request may be rejected
- The file does not contain a supported request or was modified after export.
- The request belongs to another vehicle, session or protected operation.
- The selected mode does not match the request format.
- The upstream authorization service rejects the context or is temporarily unavailable.
Operational safety
Use the token only in the workflow that generated the request. Save the request, response and relevant ISTA log together.
A prepared token does not guarantee that the vehicle connection, ECU condition or local diagnostic procedure is correct. Follow ISTA instructions and maintain stable vehicle voltage.
ONLINETOOL SERVICES
Use the online service
Understand the ISTA diagnostic token request workflow, input file preparation, processing modes, result download and common compatibility problems.
Frequently asked questions
Can one token be used for multiple vehicles?
Normally no. The request and result are tied to the context supplied by the originating workflow.
Should I enable raw/request mode?
Only when the source workflow explicitly produced a request for that mode.
What is returned by the service?
A downloadable digital result, commonly provided as a ZIP or response file assigned by the backend.
Are credits deducted on an error?
No. Credits are deducted only after the backend successfully prepares the result.