createSourcedJobPostings

Create or upsert a job posting on Indeed.

Upserting versus updating job postings on Indeed

• If you submitted the job posting on Indeed, upsert the posting.
• If another partner submitted the job posting on Indeed, update the posting. This operation is primarily for ad agencies.

Successful responses indicate that Indeed received the job posting. Indeed indexes the job and makes it available, pending spam and fraud detection, in minutes to hours. See When does my job posting appear on Indeed?.

If a job is not accepted, the corresponding CreateSourcedJobPostingResult has a null jobPosting, with an error in the standard GraphQL errors object.

To reactivate an expired job, call this mutation again with the jobPostingId and sourceName values from the expired job, just as if you were updating an active job.

To define the date that the job was reactivated in your ATS, update the datePublished field value.

You can reactivate a job for 30 days after it's expired.

After 30 days, Indeed might archive statistics and configuration related to the job. If you reactivate a job after 30 days, the API will likely return a new sourcedPostingId value. Ensure that your code can handle either the same, or a new, sourcedPostingId value.

Make sure you always save the sourcedPostingId value. You need this value to either expire jobs or reactivate expired jobs.

When you call the Indeed PLUS APIs, initiate a timeout after 5,000 milliseconds.

---

Arguments

input CreateSourcedJobPostingsInput

Response

Returns CreateSourcedJobPostingsPayload .

Example

Query

mutation CreateSourcedJobPostings($input: CreateSourcedJobPostingsInput) {
  jobsIngest {
    createSourcedJobPostings(input: $input) {
      results {
        jobPosting {
          sourcedPostingId
        }
      }
    }
  }
}

Variables

{"input": CreateSourcedJobPostingsInput}

Response

{
  "data": {
    "jobsIngest": {
      "createSourcedJobPostings": {
        "results": [CreateSourcedJobPostingResult]
      }
    }
  }
}