Pulling Jobs

Erecruit jobs are detailed in their documentation as “positions”. In order to access the Erecruit API, we need two different points of data:

1. Client ID:
2. Client Secret:

Authentication is very similar to that of Bullhorn. First we obtain our bearer token like so:

curl -XPOST 'https://erecruit.clientname.com/t/token' -d 'grant_type=client_credentials&client_id=ClientId&client_secret=ClientSecret&scope=' -H 'Content-Type: application/x-www-form-urlencoded'

After obtaining our bearer token, one such call that we can use to pull all their jobs is:

curl -v -X GET --header 'Accept: application/json' 'https://erecruit.clientname.com/webapi/Position/InternallyPosted' -H 'Authorization: Bearer bearerToken...'

Please do note that these API calls may vary slightly depending on the client. It is important to confirm with the documentation attached to the Jira or by generating it yourself using the login URL just like as was detailed in ‘What is Erecruit?’

A common schema of the fields these positions might have can look like this:

[
  {
    "ID": 0,
    "PositionTitle": "string",
    "PositionType": "string",
    "FolderGroup": {
      "ID": 0,
      "Name": "string",
      "CategoryID": 0,
      "CategoryName": "string",
      "SubCategoryID": 0,
      "SubCategoryName": "string"
    },
    "CompanyName": "string",
    "CompanyID": 0,
    "DatePosted": "2022-12-02T09:53:29.065Z",
    "DateLastOpened": "2022-12-02T09:53:29.065Z",
    "ReplyToEmail": "string",
    "HourlyMin": 0,
    "HourlyMax": 0,
    "AnnualMin": 0,
    "AnnualMax": 0,
    "Citizenship": "string",
    "YearsExperience": "string",
    "RecruiterName": "string",
    "WebPositionTitle": "string",
    "WebDescription": "string",
    "WebMin": 0,
    "WebMax": 0,
    "PrimaryOwnerID": "string",
    "Rating": 0,
    "Department": {
      "ID": 0,
      "Name": "string",
      "Phone": "string",
      "Fax": "string",
      "Address": {
        "City": "string",
        "State": "string",
        "Country": "string",
        "PostalCode": "string",
        "Latitude": 0,
        "Longitude": 0,
        "Region": "string",
        "AddressLine1": "string",
        "AddressLine2": "string"
      }
    },
    "CustomFields": [
      {
        "Name": "string",
        "FieldID": 0,
        "TypeID": 0,
        "TypeName": "string",
        "ID": 0,
        "Value": "string"
      }
    ],
    "PrimaryAddress": {
      "City": "string",
      "State": "string",
      "Country": "string",
      "PostalCode": "string",
      "Latitude": 0,
      "Longitude": 0,
      "Region": "string",
      "AddressLine1": "string",
      "AddressLine2": "string"
    }
  }
]

This can also be found within the relevant documentation. Other calls, such as finding specific recruiters by their email or ID, may also be possible as set up by their API.