Skip to main content

Problem solving examples - Job Board Workflow FAQ


Q: Do you have any recommendations for the Job Board? What path can you offer for Job Board?

A: There are generally 2 workflows for the Job Boards:


STANDARD WORKFLOW (the customers choose which jobs they want to advertise by selecting the right offer at the Advertise step in their SR account).

  • The Best example is paid job postings. The customer decides which jobs to post to what job board. But this flow is also very common for contract postings where the price equals $0.

  • The customer creates a job in SR platform and navigates to Advertise-> searches for the job board he wants to publish the job on and adds it to cart-> consumes the offer to push the job to the job board.

  • The offer has to be consumed in order for the job to be posted to the job board.

  • The job is not immediately visible on the job board! It is first sent to the job board feed.

The feed can be obtained in JSON (available in Job Board API). Some job boards will be reluctant to use JSON and will request to use XML. The XML feed is available only as an alternative to Job Board API. Our example XML feed: 

Example of our Feed

  •  If the job board wants to host the hiring process on their end the source needs to be generated so that the customer knows where the candidate comes from (candidate’s source is “Default Career Page” by default)

We generally recommend job boards to use JSON format, as it is more reliable and delivers more data. XML lacks of industry and function parameters. No matter the feed format job board needs to have an API key (X-Smart Token) in order to generate the feed. The Token is generated automatically when a job board creates an account on Partner Portal.


ALL JOBS WORKFLOW (job board posts all ACTIVE the jobs of the customer)

  • Used when the job board wants to have access to all the customer’s job postings that are active and public. The only way to get all the active jobs goes through Postings API [Customer API]. 

  • The customer has to advertise the job on the portal.

  • Each candidate will come with a default source, which can be overwritten. At the end of apply URL the job board has to add TRID so that the customer knows where the candidate comes from (candidate’s source is “Default Career Page” by default). TRID needs to be generated for each customer, please ask your Partners Consultant to help with this.

  • If you’re not a standard job board but still operate on Application API we’ll generate the source.

TRID- for postingURL

SID- for applyURL

How to get SID? Just use the same id from TRID but change TRID to SID in the URL.


Q: How can a job board conduct tests?

A: Job boards do not need (and cannot use) a sandbox account. Only whitelisted accounts can push job postings- we do not whitelist partner sandbox accounts to avoid test postings being released to external channels.


Instead of using a sandbox account, a job board can follow the workflow below to test:

  • Partner creates a test job board offer on their Partner Portal account and submits it for activation. 

  • We restrict the offer’s recipients to Partners Internal Quality Control only and activate it for $0.

  • We log in to SR Admin on Partners Internal Quality control and advertise a few jobs (2-3) through the job board offer we have just activated.

  • Email the job board that the test activation is ready, the sample postings were released to their feed, and that they can begin the integration tests.


Q: Sourcing/ how will the customers know where the candidates came from?

A: We have two possible options here:

  • If job board uses apply URL-> we generate TRID

  • If job board hosts the hiring process and uses POST candidate-> we generate source


Q: What’s “Compensation” in Job Board API?

A: Compensation reflects the salary field in Job Board API feeds. It is there by default- will display blank values when left empty. This field can only be changed after the job information has been filled (Job details-> Job Fields). This field is included ion each job by default- creating another custom field might prove confusing! 


Here’s how it looks in GET /publications response body:


 "compensation": {

        "minimum": "100000",

        "maximum": "125000",

        "currency": "USD"


Q: I advertised a job to a job board, but then made some changes to it. Will they be automatically updated and sent to the job board?

A: No, each time you introduce changes to the job posting you need to advertise the job to the job board again in order for the job board to receive the updated version of the job. A new position will appear in the “Pending” status in the job board’s feed.


Q: How to assign a screening question to one, unique job?


1) Create an Org field (here), with appropriate values, then activate it.

Do not pick the "Required" field. Make sure it is "single select" type- free text will not be saved as an "org field".

2) Go to your job, click Edit, and select the desired field.

3) Create the screening question (here), go to the "ORG FIELDS" section, and select the org fields you want it to be assigned to.

Screenshot 2020-07-03 at 17.50.53.png

Now this screening question will be available to all the jobs with "Test field 1" selected as an org field. Since we've given that org field to only one job, the screening question will be available to that one, single job only.