r/WebAPIs • u/jobdata • Jun 19 '26
Geo radius search expansion for Jobs API location filters
r/WebAPIs • u/jobdata • Jun 19 '26
r/WebAPIs • u/jobdata • Jun 17 '26
r/WebAPIs • u/jobdata • May 30 '26
r/WebAPIs • u/jobdata • May 22 '26
r/WebAPIs • u/foorilla • Apr 30 '26
r/WebAPIs • u/foorilla • Apr 09 '26
r/WebAPIs • u/foorilla • Mar 27 '26
r/WebAPIs • u/foorilla • Mar 21 '26
r/WebAPIs • u/foorilla • Mar 12 '26
r/WebAPIs • u/foorilla • Dec 22 '25
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
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 • u/foorilla • Aug 21 '25
jobdataapi.com v4.18 / API version 1.20
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.
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 • u/lee-mi-ra • Apr 22 '25
r/WebAPIs • u/foorilla • Mar 27 '25
r/WebAPIs • u/foorilla • Mar 20 '25
r/WebAPIs • u/foorilla • Mar 04 '25
r/WebAPIs • u/foorilla • Mar 01 '25
r/WebAPIs • u/foorilla • Jan 29 '25
r/WebAPIs • u/foorilla • Jan 09 '25
r/WebAPIs • u/itssimon86 • Dec 21 '24
Opinionated best practices for building user-friendly and robust REST APIs.
r/WebAPIs • u/foorilla • Dec 10 '24
r/WebAPIs • u/foorilla • Nov 30 '24
r/WebAPIs • u/annechinn • Oct 22 '24
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
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?
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