API FAQs Downloads

Sovren REST API

This documentation is for Version 10 of the Sovren REST API, released on December 15, 2020. Both V9 and V10 use the same parsing and matching engines under-the-hood, but V10 is more streamlined and has a vastly simpler output. Please visit this link for an in-depth comparison.

First Steps

  1. This documentation is for technical details about the API only. Before starting your integration, you should read the Product Documentation for the products you plan to integrate with. We will show you the most important information on how to create a quick and successful integration.
  2. Then, read the Acceptable Use Policy. There are many items in the Acceptable Use Policy that will require your programming expertise in order to be in compliance. Sovren's products and services contain open source software developed by third parties. A list of this software, including licensing and links to source code, can be found in our Open Source Disclosure.
  3. If programming in Java or C#, install the Sovren SDK using the links in the section below. Otherwise, review the code samples and endpoint documentation throughout the rest of this page.

Sovren SDK

The easiest and fastest way to get started programming your integration to the Version 10 API is by using our SDKs. We currently offer SDKs in C# and Java, with others to follow. This is, by far, the best way to use our software. You can parse a document with as little as 3 lines of code!

Each GitHub link below has installation instructions, documentation, and many code examples to help get you started. The SDKs can also be found directly using your preferred package manager.

Programming Language GitHub
C# https://github.com/sovren/sovren-dotnet
Java https://github.com/sovren/sovren-java

Code Samples

Here we have a few code samples to get you up and running quickly:

//this code uses the official SDK (see https://github.com/sovren/sovren-dotnet)
SovrenClient client = new SovrenClient("12345678", "abcdefghijklmnopqrstuvwxyz", DataCenter.US);
    
//A Document is an unparsed File (PDF, Word Doc, etc)
Document doc = new Document("resume.docx");

//when you create a ParseRequest, you can specify many configuration settings
//in the ParseOptions. See http://docs.sovren.com/API/Rest#parse-resume
ParseRequest request = new ParseRequest(doc, new ParseOptions());

try
{
    ParseResumeResponse response = await client.ParseResume(request);
    //if we get here, it was 200-OK and all operations succeeded

    //now we can use the response from Sovren to ouput some of the data from the resume
    Console.WriteLine("Name: " + response.EasyAccess().GetCandidateName()?.FormattedName);
    Console.WriteLine("Email: " + response.EasyAccess().GetEmailAddresses()?.FirstOrDefault());
    Console.WriteLine("Phone: " + response.EasyAccess().GetPhoneNumbers()?.FirstOrDefault());
}
catch (SovrenException e)
{
    //this was an outright failure, always try/catch for SovrenExceptions when using the SovrenClient
    Console.WriteLine($"Error: {e.SovrenErrorCode}, Message: {e.Message}");
}
All above code samples are provided without warranty and are not necessarily indicative of best practices.

Standard Transaction Cost

Endpoint Cost
POST /v10/parser/* 1 credit (2 credits with matching enabled, additional credits can be consumed when geocoding is enabled that follow the same structure as the POST /geocoder/* endpoint)
POST /v10/scorer/bimetric 1 credit + number of target documents * 0.1
POST /v10/matcher/* Free when initiated by a human end-user for a single transaction. (Additional credits can be consumed when geocoding is enabled that follow the same structure as the POST /geocoder/* endpoint).
When this method is called by anything other than a human end-user, this endpoint may be subject to an additional 1 credit surcharge as per the Acceptable Use Policy.
POST /v10/searcher Free when initiated by a human end-user for a single transaction. (Additional credits can be consumed when geocoding is enabled that follow the same structure as the POST /geocoder/* endpoint).
When this method is called by anything other than a human end-user, this endpoint may be subject to an additional 1 credit surcharge as per the Acceptable Use Policy.
POST /v10/geocoder/* 1 credit if using the default options. 0.1 credits if you specify your own provider key. If you use geocoding in parsing/searching/matching the same cost is applied to those transactions.
POST /v10/geocodeAndIndex/* 1 credit if using the default options. 0.1 credits if you specify you own provider key. 0 credits (free) if you specify the latitude/longitude.
GET /v10/index/{indexId}/count 1 credit. There should never be a need to call this endpoint. You control when documents are added/deleted from your indexes, so you should always know how many documents are in any given index.
GET /v10/index 10 credits. There should never be a need to call this endpoint. You should be keeping track of what indexes you have created and deleted. Adding a document to an index that doesn't exist will return a 404 - Not Found error.
GET /v10/account 1 credit. You should only call this endpoint if you are batch parsing, and you should only call it in compliance with our Acceptable Use Policy.

Note: Credit cost is increased 15% when Sovren Sourcing is enabled.

Note: Additional costs may be incurred when using deprecated versions as per the Terms of Service.

Endpoints

Notes

  • Our REST API is also documented using Swagger. Follow the links below for the appropriate data center to access an HTML page where you can make sample requests.
US Data Center EU Data Center
HTTPS https://rest.resumeparsing.com/v10/ https://eu-rest.resumeparsing.com/v10/

Authentication

Our REST API handles authentication via the Sovren-AccountId and Sovren-ServiceKey headers. These keys were generated during account creation and send to the contacts listed on the account. If authentication fails we return a 401 Unathorized HTTP Status Code.

The most common causes for unauthorized exceptions are:

  • Not including the headers in the request
  • Making requests to the wrong data center. If you have questions about which data center your account is setup for contact support@sovren.com

If you recieve a 403 Forbidden Access exception, please confirm that you are using https. We have deprecated the use of unsecured http connections in this verison.

Versioning

We continuously deploy bug fixes and new features to our API. We limit breaking changes to new versions deployed to new urls unless the change is to fix an error in the output. In the top-left of our documentation site you can change the API version of the documentation.

Release notes can be found here.

When integrating to our API, make sure that all of your API calls use same version. When upgrading to a new version it's crucial to upgrade all api calls to the new version at the same time. NEVER use multiple versions in your integration.

There are four different statuses for API versions, and they are defined as follows:

  • Suggested - this is the version we suggest that you use. It will continue to receive new features, and bug fixes as they are identified.
  • Beta - this version is currently in beta-testing. There may be some final minor tweaks before the official release.
  • Supported - do not integrate against this version, and if you're currently utilizing it plan your upgrade to the suggested version before this version is deprecated. Supported versions will continue to receive critical bug fixes, but not new features or accuracy improvements.
  • Deprecated - do not use this version. If you're integrated to a deprecated version you should plan your upgrade to the suggested version. Deprecated versions do not receive any bug fixes or new features. Deprecated versions may incur higher use of credits.

API Version Status Notes
Version 10 Beta This is the same as v9 under-the-hood, but features an entirely new/modern input/output structure and official SDKs. The output/api might have minor changes before the official release. For more info see Version 9 vs Version 10.
Version 9 Suggested This is the latest and most accurate version. If you're not already using this version please make plans to upgrade as soon as possible. Full release notes can be found here.
Version 8 Deprecated (6/26/2018) Do not integrate to v8. If you are using v8, click here to view the upgrade path.
Version 7.5 Deprecated (6/26/2018) If you're still using the version 7.5 of the API we recommend upgrading straight to version 9. The upgrade path can be found here.

HTTP Status Codes

Our API uses conventional HTTP status codes to describe the overall status of the transaction. The specific code we return are detailed below and mapped to the Info.Code values we return for every transaction:

HTTP Status Code Info.Code Description
200 - OK Success, WarningsFoundDuringParsing, PossibleTruncationFromTimeout, SomeErrors The transaction was successful
400 - Bad Request MissingParameter, InvalidParameter, InsufficientData, DataNotFound, CoordinatesNotFound, ConstraintError Unable to process request
401 - Unauthorized AuthenticationError, Unauthorized The AccountId and/or ServiceKey were invalid
403 - Forbidden N/A The request was made using http instead of https.
404 - Not Found DataNotFound The requested asset wasn't found.
409 - Conflict DuplicateAsset The request could not be completed due to a conflict with the current state of the target resource.
422 - Unprocessable Entity ConversionException The request made was syntactically correct, but the provided document was unable to be converted to text.
429 - Too Many Requests TooManyRequests Your submission has been rejected without being processed because you were exceeding the allowable batch parsing transaction concurrency limit per the AUP. You have been charged for submitting the transaction. It is your responsibility to resubmit this transaction after you correct the process which caused the concurrency problem.
500 - Internal Server Error UnhandledException An unexpected issue occurred (these are extremely rare).

Parse a Resume

POST /v10/parser/resume

Parse a single Resume/CV.

Notes

  • You can try this endpoint out at our Swagger page ( US Data Center | EU Data Center )
  • This service is designed to parse resumes/CVs. It assumes that all files passed to it are resumes/CVs. It does not attempt to detect whether a document is a resume/CV or not. It should not be used to try to extract information from other types of documents.
  • This service supports all commercially viable document formats used for text documents (image formats are not supported). The service does not support parsing of image files (such as TIFF, JPG) or scanned images within supported document file formats. Always send the original file, not the result of copy/paste, not a conversion by some other software, not a scanned image, and not a version marked up with recruiter notes or other non-resume information. Be aware that if you pass garbage into the service, then you are likely to get garbage out. The best results are always obtained by parsing the original resume/CV file.
  • If you are running batch transactions (i.e. iterating through files in a folder), make sure that you do not try to reparse a file if you get an exception back from the service since you will get the same result each time and credits will be deducted from your account.
  • Batch transactions must adhere to our Acceptable Use Policy.
  • Documents parsed by an account without AI Matching enabled will never be able to be used for matching/searching. For more information on enabling AI Matching reach out to sales@sovren.com

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Request Body

DocumentAsBase64String required string
A Base64 encoded string of the resume file bytes. This should use the standard 'base64' encoding as defined in RFC 4648 Section 4 (not the 'base64url' variant). .NET users can use the Convert.ToBase64String(byte[]) method.
DocumentLastModified required string
Mandatory date, in YYYY-MM-DD format, so that the Parser knows how to interpret dates in the document that are expressed as "current" or "as of" or similar. To find out why this is so important and how to calculate/find it, read here. Failing to pass a DocumentLastModified, or passing a DocumentLastModified that is clearly improbable, may result in rejection of data and/or additional charges, and will utterly decimate the usefulness of AI Matching. Use of the DocumentLastModified field is subject to the Acceptable Use Policy.
OutputHtml optional bool
When true, the original file is converted to HTML and stored in the Html property.
OutputRtf optional bool
When true, the original file is converted to RTF and stored in the Rtf property.
OutputPdf optional bool
When true, the original file is converted to PDF and stored in the Pdf property as a byte array.
OutputCandidateImage optional bool
When true, if the document contains inline images, the image that is most likely to be a photo of the candidate is returned as a byte array.
Configuration optional string
Optional parser configuration string to be used for parsing. If not specified, the default parser configuration will be used. For more information regarding the parser configuration string and assistance generating one, refer to the Parser Configuration Documentation.
SkillsData optional string[]
Unavailable except in special cases. Please reach out to support@sovren.com. String[] of your custom skills list names and the Sovren "builtin" skills list. If no list is provided the Sovren builtin skills list will be used. The parser automatically detects language and looks for a corresponding skills list in that language, if no match is found this list is ignored.
NormalizerData optional string
Unavailable except in special cases. Please reach out to support@sovren.com. Name of your custom normalization data file. If no list is provided the Sovren builtin skills list will be used (english only). When using custom normalization files the language to be used is determined by the Parser (the default fall back language is English if the Parser cannot find a match).
GeocodeOptions optional object
Get or insert geocode coordinate values (latitude/longitude) during the parse transaction.
Show Child Properties
IndexingOptions optional object
When your account is enabled for Matching/Searching you can automatically index documents during the parse transactions.
Show Child Properties

Response Body

Info object
Explains the outcome of the transaction.
Show Child Properties
Value object
Contains response data for the transaction.
Show Child Properties

Parse a Job Order

POST /v10/parser/joborder

Parse a single Job Order.

Notes

  • You can try this endpoint out at our Swagger page ( US Data Center | EU Data Center )
  • This service is designed to parse job orders. It assumes that all files passed to it are job orders. It does not attempt to detect whether a document is a job order or not. It should not be used to try to extract information from other types of documents.
  • This service supports all commercially viable document formats used for text documents (image formats are not supported). The service does not support parsing of image files (such as TIFF, JPG) or scanned images within supported document file formats. Always send the original file, not the result of copy/paste, not a conversion by some other software, not a scanned image, and not a version marked up with recruiter notes or other non-job order information. Be aware that if you pass garbage into the service, then you are likely to get garbage out. The best results are always obtained by parsing the original job order file.
  • If you are running batch transactions (i.e. iterating through files in a folder), make sure that you do not try to reparse a file if you get an exception back from the service since you will get the same result each time and credits will be deducted from your account.
  • Batch transactions must adhere to our Acceptable Use Policy.
  • Documents parsed by an account without AI Matching enabled will never be able to be used for matching/searching. For more information on enabling AI Matching reach out to sales@sovren.com

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Request Body

DocumentAsBase64String required string
A Base64 encoded string of the job order file bytes. This should use the standard 'base64' encoding as defined in RFC 4648 Section 4 (not the 'base64url' variant). .NET users can use the Convert.ToBase64String(byte[]) method.
DocumentLastModified required string
Mandatory date, in YYYY-MM-DD format, representing the "current" or "as of" date used during parsing. This is useful when parsing older documents. Read more about this here.
OutputHtml optional boolean
When true, the original file is converted to HTML and stored in the Html property.
OutputRtf optional boolean
When true, the original file is converted to RTF and stored in the Rtf property.
OutputPdf optional boolean
When true, the original file is converted to PDF and stored in the Pdf property as a byte array.
Configuration optional object
Options that influence parser behavior.
Show Child Properties
SkillsData optional string[]
Unavailable except in special cases. Please reach out to support@sovren.com. String[] of your custom skills list names and the Sovren "builtin" skills list. If no list is provided the Sovren builtin skills list will be used. The parser automatically detects language and looks for a corresponding skills list in that language, if no match is found this list is ignored.
GeocodeOptions optional object
Get or insert geocode coordinate values (latitude/longitude) during the parse transaction.
Show Child Properties
IndexingOptions optional object
When your account is enabled for Matching/Searching you can automatically index documents during the parse transactions.
Show Child Properties

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties
Value object
Contains response data for the transaction.
Show Child Properties

Get Account Info

GET /v9/account

Retrieve your account's current information. See Standard Transaction Cost

Notes

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties
Value object
Contains response data for the transaction.
Show Child Properties

Create an Index

POST /v10/index/{indexId}

Creates an index.

Notes

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Path Parameters

Parameter Data Type Description
indexId string The id to assign to the new index. This is restricted to alphanumeric with dashes and underscores. All values will be converted to lower-case.

Request Body

IndexType required string
The type of the index. One of: {"Resume", "Job"}

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties

Get All Indexes

GET /v10/index

Retrieves information about all the indexes associated with your account. See Standard Transaction Cost

Notes

  • You can try this endpoint out at our Swagger page ( US Data Center | EU Data Center )
  • There should never be a need to call this endpoint. You should be keeping track of what indexes you have created and deleted. Adding a document to an index that doesn't exist will return a 404 - Not Found error.

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties
Value object[]
Contains response data for the transaction.
Show Child Properties

Get Index Document Count

GET /v10/index/{indexId}/count

Retrieve the number of documents in a single index. See Standard Transaction Cost

Notes

  • You can try this endpoint out at our Swagger page ( US Data Center | EU Data Center )
  • There should never be a need to call this endpoint. You control when documents are added/deleted from your indexes, so you should always know how many documents are in any given index.

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Path Parameters

Parameter Data Type Description
indexId string The id of the index (case-insensitive).

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties
Value object
Contains response data for the transaction.
Show Child Properties

Delete an Index

DELETE /v10/index/{indexId}

Delete an index.

Notes

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Path Parameters

Parameter Data Type Description
indexId string The id of the index to delete (case-insensitive).

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties

Index a Resume

POST /v10/index/{indexId}/resume/{documentId}

Adds a single resume to an index.

Notes

  • You can try this endpoint out at our Swagger page ( US Data Center | EU Data Center )
  • Documents parsed by an account without AI Matching enabled will never be able to be used for matching/searching. For more information on enabling AI Matching reach out to sales@sovren.com

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Path Parameters

Parameter Data Type Description
indexId string The id for the index where the document should be added (case-insensitive).
documentId string The id to assign to the new document. This is restricted to alphanumeric with dashes and underscores. All values will be converted to lower-case.

Request Body

ResumeData required object
Parsed ResumeData from the Sovren Resume Parser. See Parse a Resume
UserDefinedTags optional string[]
The user-defined tags you want the document to have.

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties

Index a Job Order

POST /v10/index/{indexId}/joborder/{documentId}

Adds a single job order to an index.

Notes

  • You can try this endpoint out at our Swagger page ( US Data Center | EU Data Center )
  • Documents parsed by an account without AI Matching enabled will never be able to be used for matching/searching. For more information on enabling AI Matching reach out to sales@sovren.com

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Path Parameters

Parameter Data Type Description
indexId string The id for the index where the document should be added (case-insensitive).
documentId string The id to assign to the new document. This is restricted to alphanumeric with dashes and underscores. All values will be converted to lower-case.

Request Body

JobData required object
The parsed JobData from the Sovren Job Order Parser. See Parse a Job Order
UserDefinedTags optional string[]
The user-defined tags you want the document to have.

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties

Index Multiple Resumes

POST /v10/index/{indexId}/resumes

Adds multiple resumes to an index.

Notes

  • You can try this endpoint out at our Swagger page ( US Data Center | EU Data Center )
  • Documents parsed by an account without AI Matching enabled will never be able to be used for matching/searching. For more information on enabling AI Matching reach out to sales@sovren.com

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Path Parameters

Parameter Data Type Description
indexId string The id for the index where the documents should be added (case-insensitive).

Request Body

Resumes object[]
The list of resumes to index.
Show Child Properties

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties
Value object[]
An array of objects representing the individual document add responses. This is used to determine which documents failed in the event of an error.
Show Child Properties

Index Multiple Job Orders

POST /v10/index/{indexId}/joborders

Adds multiple job orders to an index.

Notes

  • You can try this endpoint out at our Swagger page ( US Data Center | EU Data Center )
  • Documents parsed by an account without AI Matching enabled will never be able to be used for matching/searching. For more information on enabling AI Matching reach out to sales@sovren.com

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Path Parameters

Parameter Data Type Description
indexId string The id for the index where the documents should be added (case-insensitive).

Request Body

Jobs object[]
The list of jobs to index.
Show Child Properties

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties
Value object[]
An array of objects representing the individual document add responses. This is used to determine which documents failed in the event of an error.
Show Child Properties

Get a Resume

GET /v10/index/{indexId}/resume/{documentId}

Retrieves a single resume from an index.

Notes

  • You can try this endpoint out at our Swagger page ( US Data Center | EU Data Center )
  • There should never be a need to call this endpoint. You should store/retrieve documents in your own database, since documents stored in indexes will have all PII redacted.

Request Headers

It is unnecessary to include these headers when using the Sovren SDK. Your AccountId and ServiceKey will be entered when creating a SovrenClient
Header Data Type Required Description
Sovren-AccountId string Yes The Account ID that is provided to you when establishing your Service Account.
Sovren-ServiceKey string Yes The Service key that is provided to you for access to your account’s available credits.
Content-Type string Yes Indicates the media type of the incoming request body. The only supported value is application/json.

Path Parameters

Parameter Data Type Description
indexId string The id for the index that contains the document (case-insensitive).
documentId string The id of the document to retrieve (case-insensitive).

Response Body

Info object
Information explaining the outcome of the transaction.
Show Child Properties
Value object
All of the information extracted while parsing a resume.
Show Child Properties