...
Both endpoints require authentication, in order to access them you need a token that is accuired by doing a POST against this endpoint: https://ws.di.no/ws/json/auth/v-1/login
The post should have this structure:
{
"username": "<user>",
"password": "<password>"
}
Replace <user> and <password> with the values that you acquire from the DI helpdesk. The endpoint replies with a security token that should be placed in the Authorization header like this:
"Authorization: Bearer <token>"
The token is valid for 30 minutes and is a json web token ( https://jwt.io/ ) but can be handled as a plain string on the client side.as described here: LoginV1 LoginV2
Concepts and notation
- uuid : a unique identifier returned by the service when a batch of customer addresses are submitted for processing. Is used later in a subsequent request to inform the service which batch is targeted.
- expiry : the results of a processed batch will expire a certain time after the request has been completed. The status of the batch is reported in the service response.
- proxy timeout : describes when the service will cancel outstanding requests to other authorities / source systems. All associated customer addresses will be marked as not supported, and the auhority will be set to NOT_PROCESSED
...
- expiry time : 15 minutes after the request has been processed. (TODO: Agree on / discuss this one)
- job timeout : 90 minutes (TODO: Agree on / discuss this one)30 minutes
- maximum customer addresses per request : 10'000 (TODO: Agree on / discuss this one)000
Client side
- WS-Security:
- username / password : a valid username and password is required to access the service.
- webservice access : the user must be granted privileges to access the webservice(s)
Example application
An example application can be found here: https://bitbucket.org/distributioninnovation/demo-address-check-v2-api-java/overview