Configuring Monster jobs for applicant delivery to your ATS

Jobs posted to Monster can be configured to use Flexible Apply's integration service to transmit candidate information to your applicant tracking solution.  If there is a single endpoint for processing all of your jobs and therefore a single configuration setting, contact Monster, and we can set the default configuration for your for your company - this is the most common implementation.

Alternatively, if you need to define a job-specific configuration for candidate delivery, the applicant delivery configuration parameters can be added to your Real Time Posting (RTP) implementation. For complete job posting specification detail, see the Real Time Posting Development Guide.

When an applicant delivery method is specified within your RTP specification, the parameter set must include all required fields necessary per your particular configuration. For example, if the DeliveryMethod is set to POST, a PostURL is required. The PostURL would also need to be a valid registered domain for the referenced ApiKey.

Values for the DeliveryMethod and DeliveryFormat are the following:

<xsd:simpleType name="AwmDeliveryMethodIdEnum">
- <xsd:annotation>
<xsd:documentation>1 POST    2 EMAIL    3 REQUEST     5 POST2        6 REQUEST2

<xsd:simpleType name="DeliveryFormatIdEnum">
- <xsd:annotation>
<xsd:documentation>1 JSON     2 XML</xsd:documentation>

For more technical details on these, go to the Monster enumerations schema located here. Simply search for “AwmDeliveryMethod” and "AwmDeliveryFormat". 

Take Note!  EmailAddress and PostURL in the RTP schema do not support the optional Base64 encoding of data-emailaddress and data-posturl, respectively.

Example of a POST2 delivery elements within an RTP job specification

<DeliveryMethod monsterId="5"/>
<DeliveryFormat monsterId="1"/>
<VendorText>This apply comes from a job on Monster</VendorText>

Example of a REQUEST2 delivery elements within an RTP job specification 

<DeliveryMethod monsterId="6"/>
<DeliveryFormat monsterId="2"/>
<VendorText>This apply comes from a job on Monster</VendorText>

When an applicant delivery method of "REQUEST" is specified on a job posted to Monster, an OnContinueURL parameter is specified by the client. The OnContinueURL value provided is the URL-encoded destination for Monster to redirect the applicant to continue on to any ensuring steps to be taken, such as additional interview questions.

Example OnContinueURL:

Example redirect to the client when an applicant completes the apply on a job where the OnContinueURL from above was specified:

Then the client makes a call back to Monster including the requestURL from the redirect and their shared secret. The shared secret obtained with the client's API key must be appended as an additional parameter, in the format, "&stoken=<yourSharedSecret>" to authenticate requestors.

Example Get REQUEST: ... v6GJq4FD4goGSCB9LKFX_7cq6fMHvhqsM1T_DbxvOeWOwUfzmCHs2.6pbRSK6idqUtq8ygffLlDIhA9c0-%26stoken%3d12345

This call will return the applicant information in response, candidate apply data record.

Take Note!

Be sure to specify appropriate attribution of the candidate source to Monster for candidates sourced via Apply with Monster.