Skip to content

2.2 - Return Structure

No longer offered. InfoTrie stopped collecting job-board postings from Indeed on 2026-10-29, because Indeed's terms do not allow it. This search is no longer part of the published API, and the postings it returns stop at that date. For job postings collected from employers' own career pages, see 3.1 - Standard API functions.

On Success

The answer is JSON. On the legacy path /api/idata/job_posting/indeed/search it is wrapped in the envelope below; on /api/jobs/indeed/search the body is what the envelope carries in Result.

{
     "StatusCode": 200,
     "Status": "ESUCC or EFAIL",
     "Message": "Request OK. ",
     "Debug": null,
     "Result": {}
}

Example

{ 
     "StatusCode": 200, 
     "Status": "ESUCC",
     "Message": "Request OK. Request OK. {0}",
     "Debug": null, 
     "Result": { 
          "message": {
               "description": "job posting data fetching success",
               "response_code": 3
          }, 
          "data": { 
               "total_count_available": 1, 
               "jobs": [
                    { 
                         "job_title": "data entry clerk", 
                         "job_id": "62c9ca8ce1490a2e", 
                         "company": "Randstad", 
                         "job_location": "1122 Franklin Avenue, Garden City, NY", 
                         "salary": "$18 - $22 an hour", 
                         "job_posted": "09-28-2023", 
                         "job_url": "https://www.indeed.com/rc/clk?jkxxxxxd7&vjs=3", 
                         "is_active": "yes", 
                         "job-type": "temp-to-hire", 
                         "benefits": "401(k),401(k) matching,Health insurance",
                         "job_description": "summary $18 - $22 per hour temp to perm high school category production occupations reference AB_4344209 As a Data Entry Clerk, xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxn program, and 401K contribution (all benefits are based on eligibility).", 
                         "qualification": "-", 
                         "rating": "3.7", 
                         "city": "Village of Garden City", 
                         "country": "United States" 
                    }
               ]
          }
     }
 }

Note (checked against the API on 2026-11-11)

The example was written before the current service. Today:

  • Result also carries "opSuccess": true, and message.response_code is 4.
  • total_count_available is the full number of matches; jobs holds at most 50,000 of them.
  • Each posting in jobs is returned with the fields it was stored with; the API does not reshape them. The search parameters read the field names of 2.3 - Data Dictionnary (title, active, post-date-ts, ...), not those of the example (job_title, is_active, job_posted, ...).
  • On success Message is Request OK. Request OK. {0}, as in the example. A failure has Status EFAIL, Message Request Failed. followed by the reason, Result null, and the HTTP status in StatusCode: 400 for a parameter that is unknown, malformed or out of range, or an unknown time zone.
  • A refusal of the API key or of its plan (401, 403, 429, 503) is not in the envelope: it is {"status": "error", "message": "..."}. A request that sends only the old AppKey header gets a 401 that says to send an API key in X-API-Key.