Skip to main content

1. Overview

The Get Company Jobs API returns the currently listed job postings for a given company. Results are returned synchronously in the HTTP response — no job polling required. This is a synchronous GET API — you pass a company identifier and optional pagination parameters as URL parameters, and receive a paginated array of job postings immediately. Each job in the response includes:
  • Core posting detailstitle, location, url, and a description when available
  • Work arrangementtype (e.g. full-time, contract) and a remote_allow flag
  • Compensation metadatasalary_display, min_salary, max_salary, currency_code, pay_period, and compensation_type when disclosed
  • Classificationjob_functions, industries, experience_level, skills, and benefits when available
  • Timinglisted_at_date, original_listed_date, and expire_at
  • job_id — the identifier used to fetch the complete job posting via the Get Job Details API
Common use cases:
  • Hiring signal monitoring — Track open headcount across a portfolio or competitor set to infer growth, geographic expansion, or strategic priorities
  • Talent market mapping — Pull all roles for a company to analyse function mix, seniority distribution, and locations
  • Recruiting intelligence — Surface remote-eligible or specific-function roles across a coverage universe
This API is synchronous. Results are returned directly in the HTTP response — no job submission or polling required. See How Sync APIs work.
This endpoint returns the job listing with summary fields. To retrieve the full posting — complete description, structured requirements, and all metadata — pass the job_id from this response to the Get Job Details API.

2. Quick Start

Step 1 — Make a simple request
Step 2 — Control pagination
Step 3 — Work with the jobs

3. Authentication

All requests must include a Bearer token in the Authorization HTTP header. No other authentication method is supported.
API tokens are issued from your Wokelo account. Navigate to Account Details → API Credentials in the Wokelo dashboard to get your client id and client secret. Contact support@wokelo.ai if you do not yet have API access.
Never expose your token in client-side code, browser requests, or public repositories. A missing or invalid token returns 401 Unauthorized. A valid token without sufficient plan permissions returns 403 Forbidden.

4. Request Reference

Endpoint
All parameters are passed as URL query parameters. Full request example:

5. Response

Response structure

Job object fields

Each object in the data array contains the following fields: Core posting details Compensation metadata Classification & timing

Sample response

Notes on empty fields

Many fields can be empty strings, empty arrays, empty objects, or null in valid responses. Compensation fields (min_salary, max_salary, salary_display), classification fields (job_functions, industries, skills, experience_level), and timing fields (listed_at_date, expire_at) are frequently unpopulated in the listing view — the source posting may not disclose them, or they are only resolved when you fetch the full posting via the Get Job Details API. Always guard against empty/null values before using these fields.

6. Examples

Hiring signal monitoring — paginate through all open roles

Retrieve every open posting for a company by paginating until a page returns fewer results than page_size, then summarise by location and remote-eligibility.

Chaining to the Get Job Details API

The listing view returns summary fields only. To get the full posting, pass each job_id to the Get Job Details API.
Refer to the Get Job Details API documentation for its exact endpoint path, parameters, and response schema.

7. Error Handling

The API uses standard HTTP status codes. All error responses include a JSON body with a detail or message field. Error response example:

8. Best Practices

Use the company permalink, not a display name. The company parameter expects a permalink (e.g. "tesla") or a full URL. Passing "Tesla Inc." will not resolve. Use the Company Search API to look up the permalink first. Tune page_size to your workload. Default is 50 and the maximum is 500. Use larger pages to minimise round-trips when pulling a company’s full hiring footprint; stop paginating when a page returns fewer results than page_size. Guard against empty and null fields. Most compensation, classification, and timing fields are unpopulated in the listing view. Always use .get() with defaults and check for null before using min_salary, listed_at_date, etc. Use Get Job Details for full content. This endpoint is optimised for listing and discovery. When you need the complete description, structured requirements, or resolved metadata, pass the job_id to the Get Job Details API rather than relying on the (often empty) description field here.

Get Job Details

Retrieve the complete posting for a single role by passing the job_id from this API.

Company News Monitoring

Fetch the latest AI-enriched news articles for any company.

Company Instant Enrichment

Synchronously enrich firmographic and financial data for any company by permalink or URL.