Job Update API guide

Update, clear updates, get details for, and list job postings on Indeed.

 

legal notice

By using this API and its documentation and building an integration, you agree to the Additional API Terms and Guidelines.

Job Update API workflow

Update, clear updates, get details for, and list job postings on Indeed. Calls are free and excluded from Sponsored Jobs API usage policy limits.

1. 1.
   Review Before you start - Under the single-source policy, ATSs are the source of truth for employer jobs.
2. 2.
   Authenticate.
3. 3.
   Update job posting - Ad agencies call updateSourcedJobPostings to update job posting fields.
4. 4.
   Choose a query method to get job posting information.
5. 5.
   Get job posting status by ID. If you have job IRIs, call the GraphQL node or nodes query.
6. 6.
   List job postings by criteria. For bulk job retrieval, call findEmployerJobsPartner.
7. 7.
   Clear job posting updates - Ad agencies can clear job posting updates.
8. 8.
   Check job status.
9. 9.
   Review rate limits.
10. 10.
    Troubleshoot GraphQL errors - Resolve GraphQL errors.

Job Update API references

• updateSourcedJobPostings - Ad agencies can update job posting fields.
• node - Get job posting status by ID.
• nodes - List job postings by ID.
• findEmployerJobsPartner - Lists job postings for an employer.
• clearSourcedJobPostingUpdates - Ad agencies can clear job posting updates.

The ATS controls job posting creation and expiration.

Authentication

When you become an Indeed partner, Indeed sets up an app for your integration. Sign in to Partner Console to view your app and OAuth credentials (client ID, secret, and authorization code for 3-legged OAuth). Exchange credentials for an access token to authenticate API calls.

See Integrate with Indeed and call APIs.

The findEmployerJobsPartner, node, and nodes queries require one of these OAuth token types:

OAuth token types

Token type	Description
2‑legged OAuth token that specifies an advertiser	If you are an ad agency that uses the Sponsored Jobs API with the client credentials grant type (2-legged OAuth), you already have this token type.
3-legged OAuth token	If you already have a 3-legged OAuth token, you can use it instead.

The OAuth access token must include these scopes:

• employer_access
• employer.hosted_job

For more information about adding scopes to OAuth tokens, see Scopes.

After you get an access token, include this token in the query. Indeed recommends that you refresh access tokens before they expire so that users do not need to sign in each time they view updated job statuses.

Update job posting

This feature is in beta and is not available in Japan. Contact Indeed for more information.

Upserting versus updating job postings on Indeed

• If you submitted the job posting to Indeed, upsert it.
• If another partner submitted it, update the posting. Updates are primarily for ad agencies.

Japan only: All partners except ad agencies and Indeed PLUS Publisher Network partners can update the posting.

See also:

• Upsert the posting
• Update the posting

Enables ad agencies to update job posting fields on Indeed and Indeed PLUS.

Update only jobs authorized by your client. Unauthorized updates can prevent the client from using other Indeed tools on that job. To add a location the ATS does not have, use your XML or API integration.

Workflow

To update a job posting that you did not send to Indeed:

Workflow – Update job posting

#	Description	See
1.	Choose clients to add: Contact Indeed.
2.	List job postings by criteria: Call findEmployerJobsPartner. In the response, find job postings where JobPostSurfaceStatus.isRejected is false. These jobs are searchable on Indeed. Save EmployerJob.id for later API calls.	List job postings by criteria findEmployerJobsPartner JobPostSurfaceStatus.isRejected EmployerJob.id
3.	Update job posting: To update a field such as the tracking URL or job URL, call updateSourcedJobPostings. When you update a field, later ATS changes to that field no longer appear to job seekers. For updatable fields, see UpdateSourcedJobPostingMetadataInput and UpdateSourcedJobPostingBodyInput.	Update job posting updateSourcedJobPostings sourcedPostingId EmployerJob.id UpdateSourcedJobPostingMetadataInput UpdateSourcedJobPostingBodyInput
4.	Confirm your updates: To confirm your updates, call one of these methods: findEmployerJobsPartner. Call this operation once per hour per access token. Indeed receives ATS jobs on different schedules by partner. Job updates usually appear within 30 seconds, but Indeed does not guarantee this. node query (id set to EmployerJob.id): Fetch one job to verify changes. nodes query (ids set to an array of EmployerJob.ids): Fetch multiple jobs in one call. To list sponsored jobs for a campaign, set campaignCategories to ad_campaign_category:{category}. For example, ad_campaign_category:foo returns sponsored jobs for the foo campaign.	findEmployerJobsPartner node nodes EmployerJob.id campaignCategories

For information about rate limits on this call, see Rate limits.

Request – Update job posting

To update selected fields in a job posting, ad agencies can call the jobsIngest.updateSourcedJobPostings mutation.

This operation requires an access token that represents the advertiser.

The OAuth access token must include these scopes:

• employer_access
• employer.hosted_job

See Get access token that represents employer. Instead of an employer ID, associate the token with an advertiser ID.

Provide only the fields that you want to update. To leave a field unchanged, set it to null or omit it.

This example calls the updateSourcedJobPostings mutation to update several fields in a job posting:

mutation UpdateSourcedJobPostings {
  jobsIngest {
    updateSourcedJobPostings(
      input: {
        updates: [
          {
            sourcedPostingId: "<SOURCED POSTING ID OF JOB POSTING>"
            metadata: {
              url: "https://www.example.com/jobs/123"
              campaignCategories: ["springCampaign"]
              trackingUrl: "https://www.example.com/jobs/123?utm_source=indeed"
            }
            body: {
              title: "Software Developer"
              description: "Come build the future with us!"
              jobLocation: {
                general: {
                  cityRegionPostal: "Phoenix, AZ 85003"
                  streetAddress: "1234 Sunny Lane, Phoenix, AZ 85003"
                }
              }
              salary: {
                currency: "USD"
                maximumMinor: 1000
                minimumMinor: 1000
                period: "HOUR"
              }
            }
          }
        ]
      }
    ) {
      results {
        jobPosting {
          sourcedPostingId
          employerJobId
        }
      }
    }
  }
}

mutation UpdateSourcedJobPostings {
  jobsIngest {
    updateSourcedJobPostings(input: {
      updates: [{
        sourcedPostingId: "<SOURCED POSTING ID OF JOB POSTING>"
        body: {
          description: "<h2>About the role</h2><p>Join our team as a software engineer. You design and build scalable backend services.</p><ul><li>Competitive salary</li><li>Remote-friendly</li><li>Health and dental benefits</li></ul>"
          descriptionFormatting: HTML
        }
      }]
    }) {
      results {
        jobPosting {
          sourcedPostingId
          employerJobId
        }
      }
    }
  }
}

updateSourcedJobPostings takes one argument: input, of type UpdateSourcedJobPostingsInput.

input takes one field: updates, which is an array of UpdateSourcedJobPostingInput objects. Each UpdateSourcedJobPostingInput object defines updates for one job posting.

Each UpdateSourcedJobPostingInput object takes these fields:

Request – Update job posting

Field	Type	Description
sourcedPostingId	ID!	Required. For each job posting, provide one of these values: SourcedJobPosting.sourcedPostingId, which jobsIngest.createSourcedJobPostings returns. See Create job posting. EmployerJob.id, which findEmployerJobsPartner returns. See List job postings.
metadata.url	WebUrl	The URL from the ad agency where a job seeker can apply if Indeed Apply is not available.
metadata.campaignCategories	[String!]	Category tags that group related jobs for campaign job selection. Write Sponsored Jobs API queries with ad_campaign_category:{category} for the campaignCategories values that you provide.
metadata.trackingUrl	WebUrl	The job tracking URL. When a job seeker views the job on Indeed, Indeed sends an HTTP request to this URL.
body.title	String	The job posting title.
body.description	String	The job description: Plain text (TEXT): 30 to 20,000 characters HTML (HTML): minimum 30 characters, maximum 65,000 bytes in UTF-8. The limit uses bytes. Multi-byte characters count toward the limit. See Job description formatting for supported tags. Omit the field or set it to null to leave it unchanged.
body.descriptionFormatting	DescriptionFormatting	The job description format. Set this field to HTML to enable HTML formatting. The default is TEXT.
body.jobLocation .general.cityRegionPostal	String!	Required if you update location. The city, administrative region such as state, county, or prefecture, and postal code for the job. If you set this field for a remote job, Indeed treats the job as a regional remote job.
body.jobLocation .general.streetAddress	String	The street address of the job's primary location. Include the full address, including the street name and number. Indeed can use this address to improve location-based matching and show the address to job seekers.
body.salary.currency	CurrencyCode	The salary currency code in ISO 4217 format.
body.salary.maximumMinor	Int64	The maximum salary in local minor currency. For example, the minor currency for USD is cents, so 1,000 represents $10. Set this field to null, or omit it, to clear the current value.
body.salary.minimumMinor	Int64	The minimum salary in local minor currency. For example, the minor currency for USD is cents, so 1,000 represents $10. Set this field to null, or omit it, to clear the current value.
body.salary.period	JobSalaryPeriod!	Required if you update salary. The rate used to calculate the salary, such as hourly, daily, or weekly.
body.companyName	String	Updates the company name for the job posting. To leave it unchanged, set this field to null or omit it. The maximum length is 200 characters.

For more information about these fields, see the API reference.

Confirm your updates

To verify changes, the updateSourcedJobPostings response includes job IRIs. Use the node query with the returned IRIs.

See Get job posting status by ID.

Partial updates

Field updates are not atomic. If you update more than one field in one request, the API can rarely apply only some of the changes. When this happens, the response always includes an error. However, an error response does not always mean a partial update happened. If a request that updates multiple fields returns an error, you can view the updated job posting to see which fields, if any, were updated successfully. For error handling guidance, see Troubleshoot GraphQL errors.

Response – Update job posting

updateSourcedJobPostings returns an UpdateSourcedJobPostingsPayload object. This object includes a results field, which is an array of UpdateSourcedJobPostingResult objects. Each object corresponds to one job posting update result.

Each UpdateSourcedJobPostingResult object includes a jobPosting field of type SourcedJobPostingUpdate. If Indeed does not accept the update, this field is null. Otherwise, it contains this job posting information:

• sourcedPostingId: The job posting UUID. This is the same as SourcedJobPosting.sourcedPostingId, which Indeed generated when it created the job posting. You use this value to expire or update the job posting.
• employerJobId: The job posting Indeed Resource Identifier (IRI). This is the same as EmployerJob.id.

Choose the query method to get job posting information

Use one of these methods to get job posting information:

Choose the query method to get job posting information

Method	Description
Get job posting status by ID (node or nodes query)	Use this method for direct lookup by job IRI, which is the EmployerJob ID. This method is faster than findEmployerJobsPartner when you already have job IRIs. Use cases: Update job postings and confirm changes: Call updateSourcedJobPostings to get the job IRI, which is the EmployerJob ID. Then use the node query to verify the update. Webhook: Receive the webhook, and then use the node query with the job IRI from the payload to get the current job state.
List job postings by criteria (findEmployerJobsPartner)	Use this search-based method to list all jobs. It works best for bulk inventory retrieval. Use case: Inventory sync: Sync inventory periodically when you do not have IRIs. Call findEmployerJobsPartner to bulk retrieve all associated jobs. Only legacySourceId and feedType filters are available.

Get job posting status by ID

To get job posting status by IRI, which is the EmployerJob ID, call the GraphQL node or nodes query. These queries are more efficient than list job postings by criteria.

Authentication

Use the same authentication and authorization that findEmployerJobsPartner uses. See Authentication. The OAuth access token must include these scopes:

• employer_access
• employer.hosted_job

Single job query (node)

Get one job by its IRI, which is the EmployerJob ID, with the Relay Node pattern:

query GetJob($id: ID!) {
  node(id: $id) {
    ...on EmployerJob {
      id
      jobData {
        title
        description
        company
        dateCreated
        datePostedOnIndeed
        jobLocation {
          city
          countryCode
          fullAddress
        }
        salary {
          max
          min
          period
        }
        externalPostingMetadata {
          jobPostingId
          jobRequisitionId
        }
      }
      managementUrls {
        viewJob
      }
    }
  }
}

Variables:

{
  "id": "dXJuOmluZGVlZDplbXBsb3llcmpvYjphMWIyYzNkNC1lNWY2LTc4OTAtYWJjZC1lZjEyMzQ1Njc4OTA="
}

Job IRIs (EmployerJob IDs) are base64-encoded values. The id field in the response is the encoded IRI.

See EmployerJob.

POST https://apis.indeed.com/graphql
Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json

{
  "query": "query GetJob($id: ID!) { node(id: $id) { ... on EmployerJob { id jobData { title description company } } } }",
  "variables": {
    "id": "dXJuOmluZGVlZDplbXBsb3llcmpvYjphMWIyYzNkNC1lNWY2LTc4OTAtYWJjZC1lZjEyMzQ1Njc4OTA="
  }
}

Batch job query (nodes)

Get status for multiple jobs by their IRIs (EmployerJob IDs).

Use to confirm multiple job updates, processing batches, of webhook events.

query GetMultipleJobs($ids: [ID!] !) {
  nodes(ids: $ids) {
    ... on EmployerJob {
      id
      jobData {
        title
        description
        company
        datePostedOnIndeed
        jobLocation {
          city
          countryCode
        }
      }
    }
  }
}

Variables:

{
  "ids": [
    "dXJuOmluZGVlZDplbXBsb3llcmpvYjphMWIyYzNkNC1lNWY2LTc4OTAtYWJjZC1lZjEyMzQ1Njc4OTA=",
    "dXJuOmluZGVlZDplbXBsb3llcmpvYjpiMmMzZDRlNS1mNmE3LTg5MDEtYmNkZS1mMjM0NTY3ODkwMTI=",
    "dXJuOmluZGVlZDplbXBsb3llcmpvYjpjM2Q0ZTVmNi1hN2I4LTkwMTItY2RlZi0zNDU2Nzg5MDEyMzQ="
  ]
}

Job IRIs (EmployerJob IDs) are base64-encoded values. The id fields in the response are the encoded IRIs.

See EmployerJob.

Work with webhooks

Webhook payload includes job IRI:

{
  "eventType": "job.updated",
  "jobIri": "dXJuOmluZGVlZDplbXBsb3llcmpvYjphMWIyYzNkNC1lNWY2LTc4OTAtYWJjZC1lZjEyMzQ1Njc4OTA=",
  "timestamp": "2025-12-10T15:30:00Z"
}

Use the node query with an IRI to get job posting status. For query examples, see Get job posting status by ID.

Benefits:

• Real-time updates
• Fast IRI-based retrieval
• Pre-visibility enrichment window

List job postings by criteria

Contact Indeed to use this feature. Additional requirements apply.

Lists job postings for an employer.

This call is rate limited.

If you make one call to list job postings by criteria each hour for each client, you might never reach the rate limit. However, the HTTP 429 error can still occur. If that happens, reduce your request rate. See 429 error code.

For rate limit information for this call, see Rate limits.

Request – List job postings by criteria

To list an employer's job postings, call the findEmployerJobsPartner query:

This example calls the findEmployerJobsPartner query to list job postings by criteria in descending order by the date posted on Indeed:

query FindEmployerJobsPartner {
  findEmployerJobsPartner(input: {
    filters: {
      legacySourceId: "60a9614a5d973a21",
      jobFeedType: ["INTEGRATED_FROM_PARTNER"]
    },
    sort: [{
      sortDirection: DESC,
      sortField: datePostedOnIndeed
    }]
  }, first: 10, before: null, after: null) {
    employerJobs {
      id
      jobData {
        title
        datePostedOnIndeed
        dateCreated
        description
        company
        jobLocation {
          countryCode
          city
          postalCode
          fullAddress
        }
        externalJobPageUrl
        externalPostingMetadata {
          jobPostingId
          jobRequisitionId
          campaignCategories
          trackingUrls
          rawInputLocation
          isIntegratedJob
        }
      }
      managementUrls {
        viewJob
      }
      seatsConnection {
        pageInfo {
          endCursor
          hasNextPage
          hasPreviousPage
          startCursor
        }
        seats {
          jobPost {
            id
            externalPartnerCallToAction(input: {
              locale: "en-us"
            }) {
              imageAltText
              imageUrl
            }
            status {
              globalStatus {
                isIndeedApplyActive
              }
              surfaceStatuses {
                isRejected
                isSponsorshipRequired
                isMissingRequiredSponsorship
              }
            }
          }
        }
      }
    }
    estimatedTotalResultsCount
    pageInfo {
      endCursor
      hasNextPage
      hasPreviousPage
      startCursor
    }
  }
}

findEmployerJobsPartner finds job postings by source ID or lists an employer's job postings. It takes these input fields:

List job postings by criteria fields

Field	Description
input.filters.jobFeedType	Filters jobs by feed type, which is the job source. If the feed type is UNKNOWN, you can specify two feed types. Otherwise, you can specify only one. Valid values are: CREATED_ON_INDEED. Jobs created directly on Indeed. INTEGRATED_FROM_PARTNER. Jobs integrated from partner systems, such as XML feeds or the Job API. CRAWLED_FROM_WEB. Jobs sourced from the internet. UNKNOWN. Jobs with an unknown or unclassified feed type. This can include jobs that do not yet have enough source data to assign a feed type. Default: INTEGRATED_FROM_PARTNER and UNKNOWN If your client’s jobs come from web crawling or are hosted on Indeed in Scenario 2, specify the correct jobFeedType filter. By default, findEmployerJobsPartner returns only jobs from integrations, such as XML or API feeds. For more information, see Scenario 2 details..
input.sort	Array of objects that define how to sort job postings in the response. Each object contains these fields: sortDirection: Controls whether job postings are listed in ASC or DESC order. Default: ASC. Sorts job postings by sortField from the lowest value to the highest value. sortField: Defines the field used to sort job postings. If you omit this field, sortDirection has no effect.
first	The number of job postings to return. Default: 10 Maximum: 500
before	Gets items with a cursor value before this value. Use the PageInfo object in the response to get pagination details.
after	Gets items with a cursor value after this value. Use the PageInfo object in the response to get pagination details.

Response – List job postings by criteria

findEmployerJobsPartner lists job postings for the employer associated with the access token that you use to call the API.

If you specify FindEmployerJobsPartnerInput.filter or FindEmployerJobsPartnerInput.sort in the request, the API filters and sorts the job postings in the response.

If your API token does not return the jobs that you expect, tell the user to contact their Indeed support representative through their Indeed employer account page. The representative can help connect jobs on Indeed to your advertiser or to the user's Indeed account, if appropriate.

The API returns a FindEmployerJobsPartnerConnection response object with these fields:

Response – List job postings by criteria

Field	Type	Description
employerJobs	[EmployerJob]!	An array of job posting objects. For the fields in each object, see the table in Response - View job posting.
estimatedTotalResultsCount	Int!	The estimated total number of job postings in the response.
pageInfo	PageInfo!	Pagination information.

This example response lists job postings.

The API returns only one item in seats, so startCursor and endCursor are the same, and hasNextPage and hasPreviousPage are false.

{
  "data": {
    "node": {
      "id": "aXJpOi8vYXBpcy5pbmRlZWQuY29tL0VtcGxveWVySm9iLzkxZGU0ZjVhLWE1MWYtNGQ1Ni1iOWI0LWNhMDQzZWVjNDAzMQ==",
      "jobData": {
        "title": "Certified Nursing Assistant CNA",
        "datePostedOnIndeed": "2022-03-22T20:33:28Z",
        "dateCreated": "2022-03-22T20:33:28Z",
        "description": "Anytown Health and Rehabilitation Center in Anytown, USA is a 186-bed center offering a variety of individualized, health care services for our patients and residents. We are seeking a qualified and committed team member to join our team.",
        "company": "Anytown Health and Rehabilitation Center",
        "jobLocation": {
          "countryCode": "US",
          "city": "Cambridge",
          "postalCode": null,
          "fullAddress": null
        },
        "externalJobPageUrl": "http://www.indeed.com/job/certified-nursing-assistant-cna-9354ed892ad3a1b6",
        "externalPostingMetadata": {
          "jobPostingId": "CBA-Anytown-Posting-Id",
          "jobRequisitionId": "CBA-Anytown-Req-Id",
          "campaignCategories": [],
          "trackingUrls": [],
          "isIntegratedJob": false
        }
      },
      "managementUrls": {
        "viewJob": "https://employers.indeed.com/jobs/view?employerJobId=aXJpOi8vYXBpcy5pbmRlZWQuY29tL0VtcGxveWVySm9iLzkxZGU0ZjVhLWE1MWYtNGQ1Ni1iOWI0LWNhMDQzZWVjNDAzMQ=="
      },
      "seatsConnection": {
        "pageInfo": {
          "endCursor": "YVhKcE9pOHZZWEJwY3k1cGJtUmxaV1F1WTI5dEwwcHZZbEJ2YzNRdk5EQXhOVFkxTW1OaFpEYzJZVFF4TlE9PQ==",
          "hasNextPage": false,
          "hasPreviousPage": false,
          "startCursor": "YVhKcE9pOHZZWEJwY3k1cGJtUmxaV1F1WTI5dEwwcHZZbEJ2YzNRdk5EQXhOVFkxTW1OaFpEYzJZVFF4TlE9PQ=="
        },
        "seats": [
          {
            "jobPost": {
              "id": "aXJpOi8vYXBpcy5pbmRlZWQuY29tL0pvYlBvc3QvNDAxNTY1MmNhZDc2YTQxNQ==",
              "externalPartnerCallToAction": [
                {
                  "imageUrl": "https://dlogqfjusi9uq.cloudfront.net/cta/en_US/not_searchable.svg",
                  "imageAltText": "Update needed on Indeed"
                }
              ],
              "status": {
                "globalStatus": [
                  {
                    "lifecycleStatus": "INACTIVE",
                    "isIndeedApplyActive": false
                  }
                ],
                "surfaceStatuses": [
                  {
                    "isRejected": false,
                    "isSponsorshipRequired": false,
                    "isMissingRequiredSponsorship": false
                  }
                ]
              }
            }
          }
        ]
      }
    }
  }
}

To troubleshoot validation errors, see Troubleshoot GraphQL errors. For more information about validation errors, see Validation in the GraphQL documentation.

Clear job posting updates

This beta feature is not available in Japan. Contact Indeed for more information.

An ad agency that updates a client's job posting can later clear those updates.

Workflow

An ad agency can call this operation to clear any updates it made to job postings.

For example, if you no longer plan to work with a client, use this operation to clear the updates that you made to that client's job postings. This operation restores the latest ATS data for the job posting. Your clients can then use other Indeed tools to manage the job posting again.

Workflow – Clear job posting updates

#	Description	See
1.	Update job postings: Add clients and update their job postings.	Update job postings
2.	List job postings by criteria: Call findEmployerJobsPartner, where legacySourceId is the sourcedPostingId that the update job posting operation returned.	List job postings by criteria findEmployerJobsPartner legacySourceId sourcedPostingId
3.	Clear job posting updates: Clear updated fields in a job posting. Call clearSourcedJobPostingUpdates. When you clear job posting updates, all updated fields return to the latest ATS data for that job posting.	Clear job posting updates clearSourcedJobPostingUpdates
4.	List job postings by criteria: Call findEmployerJobsPartner, where legacySourceId is the sourcedPostingId that the update job posting operation returned.	List job postings by criteria findEmployerJobsPartner legacySourceId sourcedPostingId

For rate limit information for this call, see Rate limits.

Request – Clear job posting updates

To clear fields in a job posting that updateSourcedJobPostings previously updated, ad agencies can call the jobIngest.clearSourcedJobPostingUpdates mutation.

This operation requires an access token that represents the advertiser that originally made the updates.

The OAuth access token must include these scopes:

• employer_access
• employer.hosted_job

See Get access token that represents employer. Instead of an employer ID, associate the token with an advertiser ID.

This example calls the clearSourcedJobPostingUpdates mutation to clear updates from a job posting:

mutation ClearSourcedJobPostingUpdates {
  jobsIngest {
    clearSourcedJobPostingUpdates(input: {
      updates: [{
        sourcedPostingId: "<SOURCED POSTING ID OF JOB POSTING>"
      }]
    }) {
      results {
        jobPosting {
          sourcedPostingId
          employerJobId
        }
      }
    }
  }
}

clearSourcedJobPostingUpdates takes one argument: input, of type ClearSourcedJobPostingUpdatesInput.

input takes one field: updates, which is an array of ClearSourcedJobPostingUpdateInput objects. Each ClearSourcedJobPostingUpdateInput object identifies a job posting whose updates you want to clear.

To clear updates for multiple job postings in one request, include multiple ClearSourcedJobPostingUpdateInput objects.

Each ClearSourcedJobPostingUpdateInput object takes these fields:

Request - Clear job posting updates

Field	Type	Description
sourcedPostingId	ID!	Required. For each job posting, provide one of these values: SourcedJobPosting.sourcedPostingId, which jobsIngest.createSourcedJobPostings returns. See Create job posting. EmployerJob.id, which findEmployerJobsPartner returns. See List job postings by criteria.

Response – Clear job posting updates

clearSourcedJobPostingUpdates returns a ClearSourcedJobPostingUpdatesPayload object. This object includes a results field, which is an array of ClearSourcedJobPostingUpdateResult objects. Each object corresponds to one job posting whose updates were cleared.

Each ClearSourcedJobPostingUpdateResult object includes a jobPosting field of type SourcedJobPostingUpdate. If Indeed does not accept the request to clear updates, this field is null. Otherwise, it contains this information about the job posting:

• sourcedPostingId: The job posting UUID. This value matches SourcedJobPosting.sourcedPostingId, which Indeed generated when it created the job posting. You use this value to expire or update the job posting.

• employerJobId: The job posting Indeed Resource Identifier (IRI). This value matches EmployerJob.id.

Job status

Because feed policy has changed, most jobs that you manage on Indeed no longer come from your feeds. In the past, you might have captured organic traffic data from job seekers who navigated to your career pages.

Job status

Job status	Booleans	See
Organic	“isRejected”: false “isSponsorshipRequired”: false	Organic non-sponsored jobs
Sponsored only with spend	“isRejected”: false “isSponsorshipRequired”: true “isMissingRequiredSponsorship”: false	Sponsored jobs
Sponsored only without spend	“isRejected”: true “isSponsorshipRequired”: true “isMissingRequiredSponsorship”: true
Nowhere	“isRejected”: true “isSponsorshipRequired”: false

Organic non-sponsored jobs

To get organic traffic data for jobs that are not sponsored, use one of these approaches:

Get organic traffic data

Approach		Description
1.	Add the trackingUrl field	To receive an HTTP request for each click on a job, add this field to your jobs whether or not: The job gets organic or sponsored traffic. The job uses Indeed Apply. See trackingUrl in the UpdateSourcedJobPostingMetadataInput input object.
2.	Use custom job URLs	Replace the job URL with a career page that you own, or work with ATS partners to append your tracking metadata to the job URL. If a job does not use Indeed Apply, job seekers navigate to this URL. If a job does use Indeed Apply, job seekers do not navigate to this URL. See url in the UpdateSourcedJobPostingMetadataInput input object.
3.	Collaborate with client ATS	Work with your clients and their ATS to gather organic performance data.
4.	Have clients sign in to the Indeed Analytics interface	Your clients can sign in to the Indeed Analytics interface to view complete organic performance for all jobs, whether sponsored or not. This interface gives them a full view of account data.

Sponsored jobs

To get sponsored job traffic data, call Sponsored Jobs API v8 or later to get employer job IDs that match the IDs that the Job Update API returns.

Rate limits

The Job Update API enforces rate limits on calls to these queries and mutations:

• findEmployerJobsPartner query to list job postings by criteria
• jobsIngest.updateSourcedJobPostings mutation to update job postings
• jobsIngest.clearSourcedJobPostingUpdates mutation to clear job posting updates

These limits follow best practices that help keep the API available. Indeed sets these limits above normal daily Job Update API usage, but throttles large request volumes over short periods and requires retries. To avoid hitting rate limits, spread your API requests over 10 minutes.

If you exceed a rate limit, the API returns HTTP 429, either at the HTTP level or in the errors array in the GraphQL JSON response.

You do not need to take any special action. If you need help working around these limits, request support.

If you exceed these rate limits, the API notifies you:

Job Update API rate limits

Query or mutation	Rate limit
findEmployerJobsPartner query	5 requests per second
jobsIngest.updateSourcedJobPostings mutation	20 requests per second total across both mutations
jobsIngest.clearSourcedJobPostingUpdates mutation

See also:

• RFC 6585: Additional HTTP Status Codes - 429 Too Many Requests
• Rate limiting (Indeed PLUS)

Troubleshoot errors

To troubleshoot OAuth errors that occur before you access GraphQL, see Troubleshoot OAuth errors.

To troubleshoot GraphQL errors, see Troubleshoot GraphQL errors.

These errors can occur:

• FORBIDDEN: Advertiser is in a restricted moderation status
• FORBIDDEN: You are missing permissions for this action
• FORBIDDEN: Advertiser is requesting an update to EJ
• UNAUTHENTICATED
• BAD_USER_INPUT
• NOT_FOUND
• [DOWNSTREAM_SERVICE_ERROR or INTERNAL_SERVER_ERROR](

FORBIDDEN: Advertiser is in a restricted moderation status

Example error message

{
  "errors": [
    {
      "extensions": {
        "code": "FORBIDDEN",
        "message": "Advertiser is in a restricted moderation status"
      }
    }
  ]
}

What it means

Indeed has restricted the advertiser associated with the OAuth token as a spam protection measure.

What to do

This error is unlikely. If it occurs, contact your partner manager to remove the restriction.

FORBIDDEN: You are missing permissions for this action

Example error message

{
  "errors": [
    {
      "extensions": {
        "code": "FORBIDDEN",
        "message": "You are missing permissions for this action. Ask your administrator for the permissions [Hosted_Job Create, Hosted_Job Update, Hosted_Job Read]"
      }
    }
  ]
}

What it means

The user associated with the OAuth token does not have permission to update jobs.

What to do

If an admin user did not create the OAuth client, grant job management permission to the user associated with the OAuth client. Any admin user can grant this permission in the UI. See Indeed account settings.

FORBIDDEN: Advertiser is requesting an update to EJ

Example error message

{
  "errors": [
    {
      "extensions": {
        "code": "FORBIDDEN",
        "message": "Advertiser is requesting an update to EJ (id=<EJID>), but the job is claimed by a different advertiser."
      }
    }
  ]
}

What it means

A different advertiser has already updated this job, so this advertiser cannot update it. Only one advertiser can update a job at a time.

Verify that you requested the OAuth token for the correct advertiser.

What to do

If another advertiser updated the job, this error continues until that advertiser's updates are cleared. See the clear job posting updates mutation.

This situation can occur for either of these reasons:

• The agency has access to the job through more than one advertiser.

  After the agency updates the job through one advertiser, it gets this error if it tries to update the same job through a different advertiser.

• The employer edited the job in the UI.

  The employer must remove those edits in the UI before the agency can update the job through the API.

UNAUTHENTICATED

Example error message

"extensions.code": "UNAUTHENTICATED"

What it means

Indeed cannot authenticate your request. Your OAuth token is expired or malformed.

What to do

See Troubleshoot OAuth errors.

BAD_USER_INPUT

Example error message

"extensions.code": "BAD_USER_INPUT" 

What it means

Your request contains malformed input. See the message field for details.

What to do

Fix the malformed request fields.

Check the API references for examples of correctly formatted requests:

• findEmployerJobsPartner
• updateSourcedJobPostings
• clearSourcedJobPostingUpdates

NOT_FOUND

Example error message

"extensions.code": "NOT_FOUND"

What it means

Indeed cannot find the job.

What to do

Verify that the sourcedPostingId is correct and that you requested the OAuth token for the correct advertiser. This error also occurs if the requesting advertiser does not have permission to view the job.

DOWNSTREAM_SERVICE_ERROR or INTERNAL_SERVER_ERROR

Example error message

"extensions.code": "DOWNSTREAM_SERVICE_ERROR"

Or:

"extensions.code": "INTERNAL_SERVER_ERROR"

What it means

An internal server error occurred.

What to do

Try the request again later. If the error continues, contact your partner manager.

 

Was this page helpful?