266 of 348 applications came from Indeed. The API does not export them

A commercial cleaning company in Bedford, Ohio logged 348 applications in October 2026. Indeed was the source on 266 of them. The window is October 5 through October 31.

That is 76.4%. Each of those records was delivered to an applicant tracking system Indeed had already approved. Indeed publishes APIs. None of them is a self-serve export of the applicants on a job an employer posted by hand.

In a HireClix survey published September 9, 2025, 56% of 1,000 U.S. adults named Indeed among the places they start a job search. LinkedIn was 52%. Respondents could name more than one, which is why those shares sum past 100. On June 2, 2026, Indeed’s newsroom described iCIMS data for the first quarter of the year. Employers on that platform saw nearly 59% of applicant volume from Indeed. More than 75% of the hires came from Indeed too. HireClix asked where a search starts. Indeed’s post is about hires, and it does not publish the counts under those shares. The 76.4% here is one employer, one month, and the source label on the application.

The company hires part-time cleaners for buildings around Cleveland, Columbus, and Cincinnati. It is the same employer as the September page on text replies. The listings that drew the most applications name a posted rate of $14 or $15 an hour, and an evening shift.

Where the applications came from

266 of the 348 applications carried the source Indeed. They came from 258 people. The full set was 330 people.

ZipRecruiter was next, at 51. The company’s own listings were 26, under SmartRecruiters’ label “Default Career Page.” OfferUp was 3. One application was tagged LinkedIn Limited Listings. One was tagged IndeedPro. IndeedPro stays on its own row, because that is the string on the record.

Source was not stored before October 5. That leaves 1,289 earlier applications out of the table. I do not know where they came from.

Once November has closed, this page will add that month on the same definitions. The share of these Indeed applications that replied to a text, using the reply definition on the September page, is the cut this page does not have yet.

Does Indeed have an API?

Yes. The ones that touch an applicant do not work like an export.

Indeed Apply is the delivery. The guide for direct employers says you put a postUrl on each job in the XML feed, and Indeed sends that job’s candidate information to the URL as JSON. The resume file is in the payload. The URL has to be HTTPS. If the system on the other end does not answer with a success code, Indeed retries. If delivery keeps failing, Indeed can turn Indeed Apply off for that company, or for the whole feed.

The same guide says jobs with the Easily apply badge get 12% more clicks. It does not say over what period, or out of how many jobs. A separate Indeed page says indexed jobs with Indeed Apply turned on received 40% more apply starts per job, worldwide, from January through June 2025. Jobs posted directly on Indeed use this application by default. The candidate finishes on Indeed. For a job created in Indeed’s own employer tools, the record stays there. The postUrl is a field on the feed that created the job. It is not a setting added later to a job posted by hand.

The guide says the integration usually takes about six weeks to configure, test, review with Indeed, and deploy. That clock starts after Indeed has approved the account. The page does not say how long approval takes.

Disposition Sync sends the update back to Indeed

Disposition Sync is required for Indeed Apply Sync partners. Indeed’s partner FAQ describes it as the ATS telling Indeed that an employer changed a candidate’s status, along with an anonymized application id and a timestamp. Indeed says it uses that to improve matching. It is not a feed of new applicants. A partner that does not build it risks losing Indeed Apply. Direct employers who own their feed, and do not want to share those signals, can skip it.

The system that posts the job is the system that receives the applicant

Indeed’s ATS guidelines, last updated October 2, 2026, define an ATS as the system of record for the job, the career page, and the disposition. A multisource feed has to support at least ten clients, on a launched product those clients pay for. Free trials and free tiers that allow job posting are prohibited. Jobs that started on another board, or in another ATS, are prohibited. A client cannot use a different ATS on its own website. Before a third party builds the integration for an employer, Indeed vets that third party.

The direct-employer guide adds a single-requester rule. Only the party building the integration can request and hold the API key. Indeed does not allow a proxy request, where an employer asks for a key for someone else. The developer agreement says the key holder will not share it with any third party without Indeed’s written permission, and that Indeed may refuse or end access for any reason.

What gets called Indeed automation, a hook on a job the employer already posted, is not in these documents. The path Indeed documents runs through the system that created the job.

I requested a partnership for TextWork. On October 3, Indeed’s integration team confirmed the request was in review. On October 5, they wrote that the platform was not currently meeting the ATS partnership requirements. They did not name the gaps. They said a rejected request can be resubmitted, and that senior leadership will reconsider a rejection once. TextWork receives an application after it has already landed in an ATS. It is not the system of record those guidelines describe.

100Hires published a catalog of these interfaces in October 2026. It is the clearest public map of which API is current, which is retired, and which one needs a partner. It agrees there is no self-serve public API for individual listings or for posting jobs. This page is the applicant side of that map, counted at one employer.

Method

Every application count on this page is an Applied Online report for one employer, filed by TextWork when SmartRecruiters sends a webhook for a new application.

• Application. One report per person, per job, per day. A webhook retry does not create a second row. 348 reports, from 330 people, with a stored source from October 5 through October 31, 2026. Timestamps are UTC. The first report with a source is 2026-10-05 02:15 UTC. The last in this window is 2026-10-31 23:43 UTC.
• Source. The source string on the SmartRecruiters assignment for that job, stored as it arrived. Indeed, ZipRecruiter Organic, Default Career Page, OfferUp Inc., LinkedIn Limited Listings, and IndeedPro are those strings. IndeedPro is not counted as Indeed.
• Not recorded. 1,289 Applied Online reports filed before October 5 have an empty source. 188 are from August, 1,049 from September, and 52 from October 1 through October 4. The source field was not being saved yet. Those rows are excluded, not classified.
• People. One person is one user id. The 266 Indeed applications belong to 258 people. A person who applied twice in the month is one person in that count and two applications in the table.
• The 12% and the 40%. Indeed’s figures, from the pages linked above. They were not measured in this dataset. The 12% has no published window.
• The iCIMS shares. From Indeed’s June 2, 2026 newsroom post. “Nearly 59%” and “more than 75%” are Indeed’s wording. The post names iCIMS and does not give the number of employers or applications underneath.
• HireClix. 1,000 respondents in the United States, ages 18 to 65 and older, published September 9, 2025. The 56% is a share of people who named Indeed as a place they start. It is not a share of applications.
• The partnership request. I submitted it. The October 3 and October 5 messages came from Indeed’s integration team to [email protected]. This page describes what they said. It does not quote a private attachment.

This is one company, one industry, one state, and one month of source labels. It is not Indeed’s share of the U.S. job market, and it is not a measure of who got hired.

If you are writing about this and need a cut the page does not show, by job, by city, by hour, or the underlying counts, email [email protected]. Replies go out within one business day. The employer’s name is not published here. It is available to reporters on request, as is the pay rate on each listing.