1003.API Login & Token Instructions

Access to the API interface does not use the traditional username/password login mechanism. Instead, requests must include the username and a token parameter. This token is dynamically generated through a specific algorithm based on the username, password, and specific request parameters (the password is not included in the request itself).,

Example: VIN Decoding API

The URL structure can be divided into four components: url_prefix, url_parameters, user, and token.

For example:

The general format is:

Key Components

url_prefix (fixed): http://api.17vin.com:8080

user (fixed): Your API username.

url_parameters (dynamic): Varies based on the request type:

Token Generation Algorithm,The token is dynamically generated using the following logic:

Example: username='myusername', password='mypassword', url_parameters='/?vin=LFMGJE720DS070251':

token = MD5(MD5('myusername') + MD5('mypassword') + '/?vin=LFMGJE720DS070251')

This results in the token: 92882f5ad20cf8f3330e970af12b4214

MySQL Implementation:

SELECT MD5(CONCAT(MD5('myusername'), MD5('mypassword'), '/?vin=LFMGJE720DS070251'));

Important Notes:

POST Requests: Even for POST methods, parameters must first be formatted as a GET-style 'url_parameters' string before generating the token.

Token Uniqueness: Each unique request requires a new token calculation. If 'url_parameters' changes, the token must be regenerated.,

Final URL Example:

http://api.17vin.com:8080/?vin=LFMGJE720DS070251&user=myusername&token=92882f5ad20cf8f3330e970af12b4214

(Note: This URL is illustrative and cannot be accessed directly.)