X Jobs Search API - Keyword-Based Job Discovery

Pass required query as a job keyword, such as the documented developer example, to request available X job listings. No location, salary, date or pagination inputs are documented for this read. Exact listing fields, identifiers, source references and no-match behavior have not been live-verified. Validate returned records and deduplicate using stable IDs or URLs only if they are present. Results are an observed job-discovery sample, not complete hiring-market coverage or an application-submission interface.

API Features

Job-keyword discovery input query supplies the search term; developer is the documented example for role-oriented discovery.

Documented single-filter scope Only the keyword input is provided; location, salary and date filters must not be invented.

Listing-reference validation Verify returned identifiers or URLs before choosing deduplication keys and linking to sources.

Discovery without applications The read may support a jobs digest but cannot submit applications or guarantee coverage of every vacancy.

Live API Demo

GET /api/project/twitter/jobs-search

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/twitter/jobs-search?key=<API_KEY>&query=developer'

curl -X GET 'https://api.opendata-api.com/api/project/twitter/jobs-search?key=<API_KEY>&query=developer'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Build a role-specific job-discovery digest from keyword searches, linking only to source references that are returned.
Track newly observed listings across repeated role-keyword searches after validating stable deduplication keys.
Prepare a human-reviewed public job shortlist for a developer community without inventing salary or location filters.
Compare returned samples for related role terms while labeling the dataset as observed discovery rather than a market census.

Frequently asked questions

Which filters can I use for X job listings?

Only required query is declared, with developer as the documented example. No location, salary, date or pagination inputs are documented. Validate listing fields and no-match behavior before producing a role-based digest.

Can this job search submit applications or cover every vacancy?

No. It is an observed job-discovery read, not an application interface or a complete hiring-market census. Deduplicate using stable IDs or URLs only when those references are actually returned and validated.

Related operations

Guides

View Subscription Plans →

Search Public X Job Listings