Configuring Monster jobs for applicant delivery to your ATS


Jobs posted to Monster can be configured to use Monster's Apply 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. If you are just starting your apply integration you need to register for API keys for testing and production. Contact platformpartners@monster.com or your Monster Representative and make sure to include your domains to obtain your API keys.

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 elements, the parameter set must include all required fields necessary per your particular configuration. For example, if the DeliveryMethod is set to POST2, 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:



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


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


For more schematic 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 RTP job specification



</JobBody>
<ApplyWithMonster>
<DeliveryMethod monsterId="5"/>
<DeliveryFormat monsterId="1"/>
<VendorText>This apply comes from a job on Monster</VendorText>
<PostURL>https://jobapply.atsendpoint.com/api/jobapplymonster</PostURL>
<ApiKey>EAAQLKS_bP0Z_sample_only_w--</ApiKey>

Example of a REQUEST2 delivery elements within RTP job specification 


</JobBody>
<ApplyWithMonster>
<DeliveryMethod monsterId="6"/>
<DeliveryFormat monsterId="2"/>
<VendorText>This apply comes from a job on Monster</VendorText>
<OnContinueURL>https://customerA.myats.com/continue?srcattr=monster</OnContinueURL>
<ApiKey>EAAQLKS_bP0Z_sample_only_w--</ApiKey>



When an applicant delivery method of "REQUEST2" 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: https://customerA.myats.com/continue?srcattr=monster

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

https://customerA.myats.com/continue/?srcattr=monster&requestUrl=https%3a%2f%2flogin20.monster.com%2fAwm%2fApplyRecord%3fapikey%3dEAAQ33Nb18vQ34xbnqYiR2KayESo9mwTmdI9MsrWNfAK9q4-%26adt%3dEAAQbLTWk._._X.Q0HRDx7rRSaDIX4wKzANT15yxFXNbMzJ.PDtS2QE.Gqr2XxvXLjKkuzoXS6MIkSUAANDvMzmnmDW6RlfQxgqJczTaHMhExO48rBQQWM2UCnTsjLjOhPCO2mCcn0c1F5Vrvbli5TW.fP1aB5DnR_7omWe0eanPSKO9.dagy1k0knNJKpNVbLYrwiXdyxW8279IKIrwdqCZX8pnw4K4ZxT1WUxkLK145dkNJ3.UVf30f8wkHrz5pLGwamrE4nlWXg_iAGcmJnubqCgYI5pl8Poa576v6GJq4FD4goGSCB9LKFX_7cq6fMHvhqsM1T_DbxvOeWOwUfzmCHs2.6pbRSK6idqUtq8ygffLlDIhA9c0

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:

https%3a%2f%2flogin20.monster.com%2fAwm%2fApplyRecord%3fapikey%3dEAAQ33Nb18vQ34xbnqYiR2KayESo9mwTmdI9MsrWNfAK9q4-%26adt%3dEAAQbLTWk.pUfmRb5dAUyfsnWxKWADzVmXvYNzAMK67_8gBEIXiNG4O.XOJgih1ryKveZXvNxWDzLhrqGwN_ ... 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 Monster's Apply.


Testing your integration

1. Use your testing API key so that reporting will not be affected and use the testing job board id so that real job seekers don't inadvertently find your job and apply to it.
2. Test your job posting to Monster using the testing board id 178 with your Testing Api Key and selections for method and format of delivery. Refer to RTP Testing instructions for more information on posting to the testing board.
3. Use an existing seeker account  or create one on Monster's site and create a resume. Make the resume inactive so it won't be searchable by recruiters.
4. Go to the jobview URL and click the Apply with Monster button, and sign into your job seeker account.
5. Complete Apply process for this test seeker, and close the Apply modal dialogue.
6. Verify that your service is able to receive the applicant information according to your specified delivery method. If using:
7. Repeat the Apply flow with various combinations of different resume document types (e.g., .doc, .docx, .pdf) and including and excluding a cover letter to simulate a wide range of applicant characteristics that you will encounter.