Drivers
De-identify driver data
This method requires the Drivers:Deidentification permission to be associated with your role.
For accessing the API a valid token must be passed in all the queries in the 'Authorization' header.
A valid token is generated by the API and returned by the /authenticate method by supplying a valid username and password.
The following syntax must be used in the 'Authorization' header :
Bearer aaaaaa/bbbbbb.ccccccc.ddddddBody
application/x-www-form-urlencoded
De-identification method to apply.
- expunge will delete the data from the specified fields
- obfuscate will replace the specified fields with randomised data
- wildcard-substitution will replace the specified fields with an * (asterisk character)
- wildcard-substitution-with-suffix will replace the specified fields with an * (asterisk character) preserving a 3 character suffix
Available options:
expunge, obfuscate, wildcard-substitution, wildcard-substitution-with-suffixSQL query used to identify applicable drivers for deidentification purposes.
The specified query id should return a driver_id column, identifying the drivers the de-identification process should apply to.
Success
Driver deidentification job was run and has completed successfully.