Skip to main

API Technical Specs

Learn how to configure and leverage our services to achieve your toughest recruiting needs.
SaaS     |

Create a Normalizations List

POST /v9/normalizations

Upload a custom data list to be optionally used during parsing.

This feature is not recommended and only available in special cases. Reach out to for more information.


  • You can try this endpoint out at our Swagger page ( US Data Center | EU Data Center | AU Data Center )
  • For custom normalization implementation, we recommend using the Sovren Normalization Editorutility, which provides a rich GUI for normalization management. You can download the utility from My Sovren Portal.

Request Body

A name for the data being uploaded. Names must consist of only letters, digits, and ASCII hyphens. If the combination of Name and Culture already exists, it is overwritten.
The culture or language of the data, formatted as an ISO 639-1 two letter language code. Click here for a list of supported languages currently supported by the parser.
The byte content of the normalization lists in .zip file format. Archive the normalization lists into a .zip file and pass them within this field as a Base64-encoded string of bytes.

Sample Request

{ ... 
"Name" :  "","Culture" :  "","ContentBytes" :  ""

Response Body

Information explaining the outcome of the transaction.
A response code elaborating on the HTTP status code.
The following is a list of codes that can be returned by the service:

Success – Successful transaction

MissingParameter - A required parameter wasn't provided

InvalidParameter - A parameter was incorrectly specified

AuthenticationError - An error occurred with the credentials provided
This message further describes the code providing additional detail.
Contains response data for the transaction.
The unique Key for the data list.
The Name of the data list.

Sample Request

{ ... 
{ ... 
"Code" :  "string","Message" :  "string"
{ ... 
"Key" :  "","Name" :  ""