Making a Job Live

To make a job live and available to job seekers, the job must be assigned to an available slot or credit. There are two different methods available to do this.

Method 1

The simplest method to make a job live is to use our automatic job allocation service. The following diagrams illustrate the algorithm we use. Here, Gregory has a job to post for a vacancy in London, UK. The team he belongs to has two vacant inventory items available; an Ireland credit and an EMEA slot. Gregory chooses to use the auto-allocation service. The algorithm will first check if there are any suitable credits available starting from the most specific credit first. In this case no credits are available so the service moves on to check if there are any suitable slots available starting from the most specific slot first. The algorithm finds the EMEA credit is suitable to use and makes this job live available for job applications.

Auto-Allocate-Inventory

Algorithm used by automatic job allocation service

To use the auto-allocation service send a HTTP POST request to the following URL. The {jobid} in this URL template needs to be replaced with the job id you would like to activate.


POST https://core.ws.efinancialcareers.com/v1/jobs/{jobid}/autoAllocation

Upon success, the server responds with a HTTP 204 No Content status code.

Method 2

The second method gives you more control to choose the specific inventory product you would like to use. This is a two step process.

Step One: Get inventory allocated to a team

Send an authorised HTTP GET request to the following URL. This will return all the available inventory for the team to use.


GET https://core.ws.efinancialcareers.com/v1/teams/{teamid}/inventoryAllocations

Mandatory HTTP headers


Content-Type: application/xml
Authorization: EfcAuth realm="EFC", token="522c3c4bd036a69db428ce4274745e9d"

The {teamid} needs to be replaced with a team ID the recruiter belongs to. If you remember, job slots and credits are assigned to a team so you will have to discover the team ID(s) the user belongs to. Also, brands are also assigned to a team so you will have to make sure the brand ID attached to the job also belongs to the team you have chosen.

Upon success, the server responds with HTTP 200 OK status code and an XML representation of the inventory allocated to a team.


<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<ns2:inventoryAllocations xsi:schemaLocation="http://efinancialcareers.com/schema https://core.ws.efinancialcareers.com/v1/schema">
    <ns2:inventoryAllocation>
        <ns2:id>83</ns2:id>
        <ns2:version>3</ns2:version>
        <ns2:totalAmount>20</ns2:totalAmount>
        <ns2:usedAmount>0</ns2:usedAmount>
        <ns2:inventory>
            <ns2:refId>123</ns2:refId>
        </ns2:inventory>
        <ns2:team href="https://app.ws.efinancialcareers.com/v1/teams/123">
            <ns2:refId>123</ns2:refId>
        </ns2:team>
        <ns2:jobAllocations />
        <ns2:jobAllocationsHistory>
            huge list of <ns2:jobAllocationHistory>...</ns2:jobAllocationHistory>
        </ns2:jobAllocationsHistory>
        <ns2:created>2012-05-23T08:37:44.017Z</ns2:created>
        <ns2:updated>2013-01-08T13:27:06.620Z</ns2:updated>
        <ns2:labelTranslations>
            huge list of <ns2:translation>...</ns2:translation>
        </ns2:labelTranslations>
        <ns2:dictTranslations />
    </ns2:inventoryAllocation>
    <ns2:labelTranslations>
        huge list of <ns2:translation>...</ns2:translation>
    </ns2:labelTranslations>
</ns2:inventoryAllocations>

You will need to check that inventory is available to use by making sure the <totalAmount> is greater the <usedAmount>.

Step Two: Make the job live

Send an authorised HTTP POST request to the following URL


POST https://core.ws.efinancialcareers.com/v1/jobs/2/allocation

Mandatory HTTP headers


Content-Type: application/xml

Authorization: EfcAuth realm=”EFC”, token=”522c3c4bd036a69db428ce4274745e9d”

Request Body


<jobAllocation xmlns="http://efinancialcareers.com/schema">
    <inventoryAllocation>
        <refId>1</refId>
    </inventoryAllocation>
    <job>
        <refId>2</refId>
    </job>
</jobAllocation>

The inventoryAllocation.refId is the ID retrieved from step 1 above.

Upon success, the server responds with HTTP 201 Created status code and an XML representation containing the start and end dates of the job.


<ns2:jobAllocation xsi:schemaLocation="http://efinancialcareers.com/schema https://core.ws.efinancialcareers.com/v1/schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ns2:id>1</ns2:id>
    <ns2:version>0</ns2:version>
    <ns2:startDate>2011-12-01T16:53:43.403Z</ns2:startDate>
    <ns2:expirationDate>2012-12-01T16:53:43.403Z</ns2:expirationDate>
    <ns2:inventoryAllocation>
        <ns2:refId>1</ns2:refId>
    </ns2:inventoryAllocation>
    <ns2:job href="https://core.ws.efinancialcareers.com/v1/jobs/2">
        <ns2:refId>2</ns2:refId>
    </ns2:job>
    <ns2:created>2011-12-01T17:01:48.590Z</ns2:created>
    <ns2:updated>2015-02-18T11:39:44.849Z</ns2:updated>
</ns2:jobAllocation>

Our clients include