Postings

Get postings

Get data for individual postings that match your requested filters. Note that not all fields are present for all postings, and some may be null or "Unknown".

The url field is only available for currently active postings, and the destination website is not guaranteed to be secure or functional.

Note that the score field is based on posting relevance to your query. Many fields have a single value per posting so relevance scores will be the same for

all postings that match those filters. Score variance occurs when a filter is provided that can match a subset of the values in a particular field, filters such as

certifications and skills provide such functionality. Only the first 200 values per filter will be used for relevance scoring.

To request more postings please contact us here.

<div class="internal-only">

Posting Data Source Access and Limits

To restrict their access to only expired posting data, give postings:only_expired_samples claim.

By default all clients can view up to a total of 10 postings. The limit can be changed through a postings:samples_full_access claim. The claim postings:samples_full_access alone increases the total limit to 100 postings. To increase the limit to 1000, grant postings:samples_full_access:1000.

</div>
post/postings

Request

  • Base URL
    https://api.lightcast.io/global-postings
  • URL
    https://api.lightcast.io/global-postings/postings
  • Auth
    OAuth 2
    Client credentials
    Token URL: https://auth.emsicloud.com/connect/token scopes: postings:global

Query parameters

lot_version'6' | '7'
Example:7

Specify LOT taxonomy version to use.

area_version'lf_area_2023_2' | 'lf_area_2025_1'
Example:lf_area_2025_1

Specify area taxonomy version to use.

area_laa_version'1' | '2'
Example:2

Specify LAA area taxonomy version to use.

new_taxonomy_versionstrue | false

Use new taxonomy versions.

Request body

fieldsstring[]

See /meta postingsFields for available fields.

limitinteger

Maximum: 10 (or more for authorized consumers)

orderstring[]

Postings are sorted with respect to the order of the provided keys.

  • score - sort postings according to their relevance to the request filter.
  • posted - sort postings by their posted dates.

I.e. using an order of ["score", "posted"] will sort postings first by their score then sort the ones with the same score by posted dates.

pageinteger

Example request

{
  "filter": {
    "active_sources_info": {
      "type": "Company",
      "source": "ABCRecruiting.com",
      "url": "ABCRecruiting.com/job/GNkBaDoMWiyQbmlpFHfz"
    },
    "when": {
      "start": "2018-06",
      "end": "2019-06"
    },
    "company_is_staffing": true,
    "posting_duration": {
      "upper_bound": 30
    },
    "min_years_experience": {
      "lower_bound": 1,
      "upper_bound": 3
    },
    "max_years_experience": {
      "lower_bound": 4,
      "upper_bound": 6
    },
    "min_salary": {
      "lower_bound": 55000,
      "upper_bound": 80000
    },
    "max_salary": {
      "lower_bound": 55000,
      "upper_bound": 80000
    },
    "salary": {
      "lower_bound": 50000,
      "upper_bound": 200000
    }
  }
}

Response

OK

Changes

No recorded changes to this operation across all 1 revision of this API.