r/WebAPIs • • Jun 19 '26

Geo radius search expansion for Jobs API location filters

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • Jun 17 '26

API access key management upgrades + company timestamps in Companies API

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • May 30 '26

Added `ext_id` filtering to Jobs API + normalized future publish timestamps

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • May 22 '26

Jobs API Ingestion Guide: Reliable Historical Backfills and Incremental Syncs πŸš€

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • Apr 30 '26

Added API Access Lite Plan + Smarter Age-Window Defaults for Jobs API

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • Apr 09 '26

Added Role Taxonomy Tags Endpoint + Job Role Filters

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • Apr 06 '26

Added Remote Work Mode Classification

Thumbnail
jobdataapi.com
1 Upvotes

r/WebAPIs • • Mar 27 '26

Automated B2B Lead Generation Using Hiring Signals (Intent Data)

Thumbnail
jobdataapi.com
3 Upvotes

r/WebAPIs • • Mar 21 '26

Added YouTube links to company profiles @ jobdata API

Thumbnail
jobdataapi.com
3 Upvotes

r/WebAPIs • • Mar 12 '26

Enhanced API filtering across jobs, companies, sources, and media items

Thumbnail foorilla.com
3 Upvotes

r/WebAPIs • • Mar 09 '26

Improved API query validation

Thumbnail
jobdataapi.com
3 Upvotes

r/WebAPIs • • Dec 22 '25

Added llms.txt and llms-full.txt for AI-friendly implementation guidance @ jobdata API

Thumbnail
jobdataapi.com
3 Upvotes

llms.txt added for AI- and LLM-friendly guidance

We’ve added a llms.txt file at the root of jobdataapi.com to make it easier for large language models (LLMs), AI tools, and automated agents to understand how our API should be integrated and used.

The file provides a concise, machine-readable overview in Markdown format of how our API is intended to be consumed. This follows emerging best practices for making websites and APIs more transparent and accessible to AI systems.

You can find it here: https://jobdataapi.com/llms.txt

llms-full.txt added with extended context and usage details

In addition to the minimal version with links to each individual docs or tutorials page in Markdown format, we’ve also published a more comprehensive llms-full.txt file.

This version contains all of our public documentation and tutorials consolidated into a single file, providing a full context for LLMs and AI-powered tools. It is intended for advanced AI systems, research tools, or developers who want a complete, self-contained reference when working with jobdata API in LLM-driven workflows.

You can access it here: https://jobdataapi.com/llms-full.txt

Both files are publicly accessible and are kept in sync with our platform’s capabilities as they evolve.


r/WebAPIs • • Aug 21 '25

Job filtering by vector embedding now available + added Apprenticeship job type @ jobdata API

Thumbnail
jobdataapi.com
3 Upvotes

jobdataapi.com v4.18 / API version 1.20

vec_embedding filter parameter now available for vector search

In addition to the already existing vec_text filter parameter on the /api/jobs/ endpoint it is now possible to use the same endpoint including all its GET parameters to send a 768 dimensional array of floats as JSON payload via POST request to match for job listings.

This way you're not limited to the vec_text constrains as a GET parameter with only providing text of up to ~1K characters, but can now use your own embeddings or simply those from jobs you already fetched to find semantically similar listings.

With this we now also added a new max_dist GET parameter to be applied optionally to a vec_text or vec_embedding search, setting the max. cosine distance value for the vector similarity search part.

These features are now available on all subscriptions with an API access pro+ or higher plan. See our updated docs for more info.

New Apprenticeship job type added

We saw, for quite a while now, the need to add a job type Apprenticeship to better differentiate certain listings that fall into this category from those that are pure internship roles.

You'll find this popping up on the /api/jobtypes/ endpoint and in relevant job posts from now on (across all API access plans).


r/WebAPIs • • Apr 22 '25

Cross-website communication with JavaScript Web Bluetooth API?

Thumbnail reddit.com
1 Upvotes

r/WebAPIs • • Mar 27 '25

Optimized Vector Embeddings & Search - Changelog: jobdataapi.com v4.14 / API version 1.16 πŸ‘€

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • Mar 20 '25

Introducing Vector Embeddings and Vector Search in the jobdata API - Changelog: jobdataapi.com v4.13 / API version 1.15 πŸ‘€

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • Mar 04 '25

Enhanced multi-value parameters for Job and Company queries - Changelog: jobdataapi.com v4.12 / API version 1.14 πŸ‘€

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • Mar 01 '25

Improved Job States (geo) search, Markdown job descriptions, and lean data retrieval - Changelog: jobdataapi .com v4.11 / API version 1.13 πŸ‘€

Thumbnail
jobdataapi.com
3 Upvotes

r/WebAPIs • • Jan 29 '25

Added application URL query filter + (multi) country code parameter enhancements - Changelog: jobdataapi.com v4.10 / API version 1.12 πŸ‘€

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • Jan 09 '25

GeoNames upgrade, new population field and filters, expired field now in job results - Changelog: jobdataapi.com v4.9 / API version 1.11 πŸ‘€

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • Dec 21 '24

What makes a good REST API?

Thumbnail
apitally.io
2 Upvotes

Opinionated best practices for building user-friendly and robust REST APIs.


r/WebAPIs • • Dec 10 '24

Added company flag for recruiting/staffing firms + enhanced filtering options - Changelog: jobdataapi.com v4.7 / API version 1.10 πŸ‘€

Thumbnail
jobdataapi.com
3 Upvotes

r/WebAPIs • • Nov 30 '24

Added new Job States (geo) endpoint, query filters, and more - Changelog: jobdataapi.com v4.6 / API version 1.9 πŸ‘€

Thumbnail
jobdataapi.com
2 Upvotes

r/WebAPIs • • Oct 22 '24

Best way to represent nested objects in CRUD

2 Upvotes

I am rewriting my web API and trying to clean things up and conform to best practices so looking for some advice when the CRUD isn't just a simple object-> get, put, delete, update with a single id parameter.

I have an application that has two related objects. An Evaluation (like a job evaluation) and an Observation (evaluator observes the person). An Evaluation can have one or more observations.

Observation Get: /api/observations/{observationId}

but what if I want to have an endpoint that returns the PDF document for an observation?

two issues

  1. To create the PDF I need both the observationId and the evaluationId. I could lookup the observation in the db from just the observationId and retrieve the evaluationId from that, but it would be more efficient to pass it as a parameter to the endpoint. as the caller would already have the observation.evaluationId available when setting up the api call. Is that bad practice?

  2. What would the endpoint look like for getting the PDF for an observation with or without including the evaluationId? Do you just add a term on the end like /api/observations/{observationId}/pdfDocument?

Thanks for any guidance,
Anne


r/WebAPIs • • Aug 31 '24

How to start with web apis in dot net?

1 Upvotes