Job Post
The process detailed on the Job Post Standard Integration page involves the push notification step and its response. The high-level process involves sending a POST containing a system ID and the information about the job to be posted, and then expecting a reply providing the Platform with a link that is used to direct the user to the appropriate URL to complete the job posting process. The following outlines the process for posting a job to the Web.
The Job Post Event occurs when the user navigates to the Source tab on a Job Profile inside iCIMS. From the Source tab, the user will then first access the Career Portal Posting panel to post a job to an iCIMS Career Portal, and will then access the Job Board Posting panel to post a job to a Partner's site. (Note that the job must be posted to at least one iCIMS Career Portal before the user can post it to a Partner's site.) This UI interaction will generate a POST request to the external job posting partner, who will then return the URL that can be used to finish the transaction. The Platform will then launch a page pointed at this URL. The payload will be a JSON message containing the following parameters used to describe the request:
Parameter | iCIMS Field Mapping | Purpose |
systemId | Job System ID | Specifies the job to be posted. May be used to query the job by ID using existing Web Services at api.icims.com |
portalUrl | Portal URL | Specifies the URL on the Portal that is used in applying for the job |
eventType | Event Type | Specifies event type, which can be JobPostToWebEvent or JobUnpostToWebEvent |
customerId | Customer ID | Specifies the ID of the customer |
userId | User System ID | Specifies the user who initiated the request |
The partner may issue a Web Service request to obtain additional details about the job in question.
The server should acknowledge the response with any of the following HTTP response codes:
- HTTP 303 See Other
- HTTP 400 Bad Request
The criteria for issuing these responses should be as follows:
- 303 See Other: The job post initiation request was successful, and the user should be redirected to the specified URL to complete the process.
- 400 Bad Request: The job post initiation request was not successful. Must be accompanied by a message to be displayed to the user.
Additionally, a JSON message should be returned with the following parameters:
- technicalMessage: a message specifying the technical outcome
- userMessage: a user-friendly message that may be displayed, indicating the outcome
Example:
iCIMS -> Job Post Partner:
POST /JobPost/iCIMS/iCIMS.asp HTTP/1.1
Host: import.example.com
Content-Type: application/json;charset=UTF-8;charset=UTF-8
Content-Length: 248
Link: api.icims.com/customers/1234/jobs/1289;rel="job";title="Job Profile",
api.icims.com/customers/1234/people/400;rel="user";title="Posting User"
Date: Fri,06 Dec 2012 16:25:14 GMT{
"systemId":"1289",
"portalUrl":"jobs-customer.iCIMS.com/jobs/1289/login",
“eventType”:“JobPostToWebEvent”,
"customerId":"1234",
“userId”:“400”
}
The Job Post event is used by iCIMS to send job information to a third party vendor when a user selects to post a job externally in the iCIMS platform. This event is most commonly used by iCIMS clients wishing to send jobs to third party aggregators.