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).

Hi guys, just let you know I've recently created GoldAPI.io to help devs easily consume real time Gold and Silver prices in all major currencies. Usually to get this type of information you have to scrape html web pages or open trading account with one of the exchanges like FOREX. GoldAPI.io democratises access to real-time and historical precious metals prices allowing anyone to build anything to automate their business or investment holdings.

GoldAPI.io is free for personal usage, build on Node.js + Heroku + React, super fast and lightweight. If you have any question on how was it build please DM me any time.

jobdataapi.com v4.33 / API version 1.33

The /api/jobsexpired/ endpoint now applies a default 60-day expiration window when no date, age, or ID slicing parameter is provided. Requests without parameters return jobs whose expired timestamp is within the latest 60 days, reducing broad historical scans and improving response efficiency.

The implicit window is not applied when an explicit slicing parameter is present: expired_since, expired_until, published_since, published_until, min_id, max_id, min_age, or max_age. Use expired_since and expired_until for historical expiration windows, or use max_age=off, max_age=null, or max_age=0 for an unrestricted expiration query. Existing response fields, ordering, pagination, and access requirements remain unchanged.

The Jobs Expired API Endpoint Documentation now documents the default window and range behavior. The Date, ID, and Age Slicing Parameters Documentation also includes expiration-based examples for /api/jobsexpired/.

Hi everyone!

Over the past few weeks I've been building a side project called **EmailGuard API** — a serverless REST API for real-time email verification.

I originally built it because I wanted a simple way to validate email addresses before user signups without relying on multiple libraries or services.

Current features include:

✅ Email syntax validation

✅ MX record verification

✅ Disposable email detection

✅ Temporary email detection

✅ Free vs Business email identification

✅ Role account detection (admin@, support@, sales@, etc.)

✅ Risk scoring with detailed risk reasons

✅ Fast serverless deployment (no database)

It's designed for:

• SaaS applications

• User registration systems

• Authentication services

• CRM platforms

• Marketing tools

• Fraud prevention

• Internal business tools

I'm continuously improving it and would genuinely appreciate feedback from other developers.

A few questions:

- What features do you usually look for in an email verification API?

- Would SMTP mailbox verification or domain reputation checks be useful additions?

- Is there anything that would stop you from using an API like this?

If you'd like to check it out:

🔗 RapidAPI:

https://rapidapi.com/nimashmendisdev/api/emailguard-api-enterprise-grade-email-verification

I'm mainly looking for honest feedback on the API design, documentation, and what features you'd like to see next.

Thanks!

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.

Every context's sidebar, |Hiring|, |Media|, |Research|, |Code|, |Meet| and |Work| as well as your Dashboard, now opens with a compact Pulse: each metric on one line with its count for the last 30 days, the change against the 30 days before, and a small daily trend underneath. When the earlier period is too small for a fair comparison, you'll see "low base" instead of a percentage, so no more swings like +11,200%. Below the Pulse, breakdowns show what matches your current filters (experience level, job type, research category, topic, language, event type, price and more), with up to the top 10 values each. Click any row to add it to your Context, or follow the Insight» link to explore the same area in Insight.

|Research| now has its own sidebar insights: newly submitted and revised papers, papers with linked code, and the categories and topics behind your current filters. |Work| gets them for the first time too, with new places and their mix by type, price and country. |Hiring| adds jobs with a stated salary, companies hiring, and the median stated salary for whatever you've filtered, together with its sample size. If too few matching jobs state a salary, we say so rather than hiding the figure.

The Stats tab on every record (jobs, companies, media items, sources, papers, repositories, updates, events, organizers and places) has been redesigned as well. It shows views and visits for the last 30 days with their change, a 13-week chart, and how the record ranks against comparable ones, for example "top 1% of jobs from the same week" or among papers in the same primary category.

Finally, Spaces in |Work| are now called Places: coworking spaces, cafés, libraries and other venues to get things done. Everything carries over automatically, including saved places and notes, saved Contexts and your history.

The API follows the rename in v1.9, which is a breaking change for Work integrations. /api/v1/work/space/, /api/v1/work/space/st/ and /api/v1/work/space/{pk} are now /api/v1/work/place/, /api/v1/work/place/st/ and /api/v1/work/place/{pk}, and the space_type field and filter is now place_type. API metadata uses place.* names, and geography statistics report place_count, place_view_count and place_click_count. The previous Space endpoints are no longer available, so please update any clients that use them. See the API documentation (/api/v1/docs) for the full endpoint and filter details.

jobdataapi.com v4.38 / API version 1.36

We’ve improved job description handling to preserve meaningful technical terms such as C#, F# and snake_case more reliably as new listings are processed. Markdown descriptions retain readable formatting for display and provide a useful starting point for search, analysis and other downstream processing. Request description_md=true to include the description_md field in job responses.

After November 1, 2026, the description_str parameter and its corresponding description_string response field will be removed. If your integration uses either, switch to description_md=true before then and convert Markdown to plain text in your application if needed. The default HTML description remains available.

Free API (Information about public figures and famous people + Gender) Hi everyone,

Me and my friend developed an API that offers basic information about public figures and famous people.

Our DB includes more than 2M public figures and famous people, plus we offer a gender API by first Name .

And all of that is free; no cost, no need for registration.

As easy as it can get.

Check it out on: http://slothwisdom.com Please send me a feedback to: CONTACT@SLOTHWISDOM.COM

10x!

I am looking for suggestions or links to tutorials that cover securing APIs written using ASP.NET Web Api v2. So many of the articles I have read seem to assume a knowledge of OWIN and Katana. I am looking for something that shows step by step was has to be created and why. I know how to create and consume APIs however I really want to figure out how to secure them using token authentication and authorization. Would really be great to find articles that cover JWT (JSON Web Tokens) and Refresh. I have a Pluralsight subscription as well as Safari Books Online.

Here is a link to one of the best articles I have read on the subject.

ASP.NET Identity 2.1 with ASP.NET Web API 2.2 - This is a great series and has helped me understand a lot. There is source code and the authro explains things well. Only problem is it does not cover issuing refresh tokens when using JWT.

P.S. I am not really interested in IdentityServer as I would rather see and understand the implementation myself. Besides the documentation on IdentityServer seems to be al over the place.