Introduction
The Parse API (Lens API) provides access to Lightcast resume and job parsing capabilities, enabling you to extract structured data from unstructured documents. Use the API to transform resumes and job descriptions into machine-readable data for search, analytics, recruitment, and talent intelligence workflows.
The API supports common document formats, including DOC, DOCX, HTML, RTF, PDF, ODT, TXT, WPD, and WPS.
You can use the parsed data in recruitment systems, talent intelligence platforms, and HR data ingestion workflows.
Get API Access Credentials
The Parse API requires security credentials to access protected resources. After signing in, you can find your credentials under Profile > OAuth Settings.
You need the following four credentials to access protected resources in the Parse API:
- Consumer Key
- Consumer Secret
- Parse API Access Token
- Parse API Access Token Secret
Generate Authorization Header
Download the OAuthGeneration library and add it to your application.
Use the OAuthGeneration library to generate the authorization header, as shown in the following examples.
OAuthGeneration oAuth = new OAuthGeneration("WEB_SERVICE_URL", "HTTP_METHOD", "CLIENT_ID", "CLIENT_SECRET", "API_ACCESS_TOKEN", "API_ACCESS_TOKEN_SECRET");
String oAuthString = oAuth.GetOAuthString();string oAuthString = OAuthGeneration.OAuth.GetOAuthString("WEB_SERVICE_URL", "HTTP_METHOD", "CLIENT_ID", "CLIENT_SECRET", "API_ACCESS_TOKEN", "API_ACCESS_TOKEN_SECRET");$oAuth = new OAuthGeneration("WEB_SERVICE_URL", "HTTP_METHOD", "CLIENT_ID", "CLIENT_SECRET", "API_ACCESS_TOKEN", "API_ACCESS_TOKEN_SECRET");
$oAuthString = $oAuth->GetOAuthString();oAuth = OAuthGeneration("WEB_SERVICE_URL", "HTTP_METHOD", "CLIENT_ID", "CLIENT_SECRET", "API_ACCESS_TOKEN", "API_ACCESS_TOKEN_SECRET")
oAuthString = oAuth.GetOAuthString()Authentication
API Authentication Using OAuth 1.0
API Authentication Using OAuth 1.0
Every API call is authenticated using the OAuth 1.0 standard. Each HTTP request must include an OAuth authorization header using the authentication information provided by Lightcast.
The OAuth Consumer Key (oauth_consumer_key) maps to a client, while the OAuth Token (oauth_token) maps to the API being accessed.
Requests are scoped to the client identified by the OAuth Consumer Key. For example, a GETrequest to a URI returns results associated with the client specified by the OAuth Consumer Key.
Lightcast supports the following OAuth signature methods:
HMAC-SHA1RSA-SHA1
The
PLAINTEXTsignature method is not supported.
Configure Request and Response
To use the Parse API, prepare the request data in the format required by the endpoint.
The API accepts both XML and JSON request data.
Use the Content-Type header in the HTTP request to specify the format of the request data. Use the Accept header to specify the format of the response.
The API can return either XML or JSON formatted responses based on the Accept header.
Use the following media types:
application/xmlfor XMLapplication/jsonfor JSON
Request Parameters
Send an HTTP request to the appropriate Parse endpoint with the following information:
- Authorization header
Content-TypeandAcceptheaders- Endpoint URL
- Request data
Download the LensApiClient library and add it to your application.
You can use the LensApiClient library to send requests to the API as follows:
LensApiClient apiClient = new LensApiClient();
String response = apiClient.sendLensApiRequest("WEB_SERVICE_URL", "HTTP_METHOD", oAuthString, "ContentType", "AcceptType", "REQUEST_BODY");Response Parameters
| Name | Description |
|---|---|
RequestId | Unique ID for each request. You can use this ID to query the API logs. |
Timestamp | Timestamp indicating when the request was made. For example, 2020-12-12 22:36:45.220. |
Status | Indicates whether the request succeeded or failed. |
StatusCode | HTTP response status code. Refer to the Best Practices page for more details about the possible status codes. |
ResponseData | An object containing the parse response. For successful requests, it contains the parse response data. For failed requests, it contains an error message. Refer to the endpoint documentation for details about the response object structure. |
Status Code Summary
| Code | Meaning | Description |
|---|---|---|
| 200 | OK | Request was successful. |
| 400 | Bad Request | The request was unacceptable, often due to missing a required parameter. |
| 401 | Unauthorized | Authentication error. |
| 404 | Not Found | Resource not found. |
Next Steps
Download the sample code from here.
Before running the sample, make sure the following values are configured:
| Name | Description |
|---|---|
WEB_SERVICE_URL | REST/SOAP URL |
HTTP_METHOD | HTTP method |
CLIENT_ID | Consumer Key |
CLIENT_SECRET | Consumer Secret |
API_ACCESS_TOKEN | Parse API access token(Based on the api which you are going to use) |
API_ACCESS_TOKEN_SECRET | Parse API access token secret. |
CONTENT_TYPE | application/xml or application/json |
ACCEPT_TYPE | application/xml or application/json |
REQUEST_BODY | XML/JSON formatted data to be posted to the API |
For a complete list of HTTP status codes and their meanings, refer here.

