Tidy the supplied name, standardising casing and punctuation. The gender is derived from the name where possible, and standard formal and informal salutations are generated.
To connect to this service you'll need to use one of these endpoints:
Protocol | URL |
---|---|
JSON |
JSON
https://webservices.data-8.co.uk/NameCleansing/CleanName.json |
OPEN API |
OPEN API
https://webservices.data-8.co.uk/swagger/NameCleansing/swagger.json |
SOAP |
SOAP
https://webservices.data-8.co.uk/namecleansing.asmx |
Name | Description |
---|---|
username | username
See the available authentication methods. If you are using username & password authentication, specify the username to authenticate as. If you are using API Key authentication and you are not using the JSON, Javascript or ADO APIs, use your API Key here with the prefix |
password | password
If you are using username & password authentication, specify the password to use for authentication. Otherwise leave this blank. |
name | name
The name to clean, supplied in four separate fields:
If you have a name in one field, use the |
options | options
An array of options that control further details of how this method operates. See the |
option
parameter. Each option is specified as a key/value pair.
The list of available names is shown below, along with a description of the allowable values for that name.
Name | Description |
---|---|
Common Options | |
ApplicationName |
ApplicationName
Gives the name of the calling application - used to break down usage by application in the usage reports on the dashboard.
|
Name | Description |
---|---|
Status | Status
Indicates whether the method call was successful, or if some error occurred. If the |
Name | Name
A tidied version of the supplied |
Gender | Gender
The gender that has been identified from the name. This can be one of the following values:
|
FormalSalutation | FormalSalutation
The mode of address that should be used for this person in a formal situation. |
InformalSalutation | InformalSalutation
The mode of address that should be used for this person in an informal situation. |
Each request to this method consumes 1 NameCleansing credit.
Request Format
{ "name": { "Title": "Mr", "Forename": "John", "MiddleName": "", "Surname": "Smith" }, "options": {} }
Response Format
{ "Status": { "Success": true, "CreditsRemaining": 1000 }, "Name": null, "Gender": "Unknown", "FormalSalutation": null, "InformalSalutation": null }
Depending on your chosen authentication method you will need to modify this request slightly:
API Key
https://webservices.data-8.co.uk/NameCleansing/CleanName.json?key=your-api-key
and do NOT include the
username
or password
properties in the request JSON document.
Username and Password
https://webservices.data-8.co.uk/NameCleansing/CleanName.json
and include
username
and password
properties in the request JSON document.Do not use for client-side requests!
JWT Token
https://webservices.data-8.co.uk/NameCleansing/CleanName.json
Include the JWT token in the request headers as:
Authorization: Bearer your-jwt-token
Parameter | Value |
---|---|
Parameters | |
Name | |
name | Title
Forename
MiddleName
Surname
|
Common Options | |
ApplicationName |
ApplicationName
|
Credits Remaining Today: 5 |