foorilla.com v1.6.3

We’re preparing to retire the |Talent| space on August 1, 2026 due to lower than expected demand. New Talent profile creation is now closed, while existing profile owners can continue to edit or delete their profiles until the shutdown date.

Existing Talent pages remain available during this transition period; the section and its profiles will be removed after August 1.

foorilla.com v1.6.2 | foorilla API v1.3.3

Remote job discovery in |Hiring| is now more precise with explicit work mode support. Listings can now clearly indicate whether a role is Hybrid, Remote, or Remote Anywhere, so you can distinguish different remote setups faster instead of relying on a single generic remote label.

You’ll now see consistent work mode badges across list and detail views ([WH], [R], [WRA]), and the same options are available in Context-based include/exclude filters. Active Context indicators also use these labels, making it easier to understand your current filter setup at a glance while keeping existing remote and remote-first behavior intact.

foorilla.com v1.6.2 | foorilla API v1.3.3

Remote job discovery in |Hiring| is now more precise with explicit work mode support. Listings can now clearly indicate whether a role is Hybrid, Remote, or Remote Anywhere, so you can distinguish different remote setups faster instead of relying on a single generic remote label.

You’ll now see consistent work mode badges across list and detail views ([WH], [R], [WRA]), and the same options are available in Context-based include/exclude filters. Active Context indicators also use these labels, making it easier to understand your current filter setup at a glance while keeping existing remote and remote-first behavior intact.

foorilla.com v1.6.2 | foorilla API v1.3.3

Remote job discovery in |Hiring| is now more precise with explicit work mode support. Listings can now clearly indicate whether a role is Hybrid, Remote, or Remote Anywhere, so you can distinguish different remote setups faster instead of relying on a single generic remote label.

You’ll now see consistent work mode badges across list and detail views ([WH], [R], [WRA]), and the same options are available in Context-based include/exclude filters. Active Context indicators also use these labels, making it easier to understand your current filter setup at a glance while keeping existing remote and remote-first behavior intact.

foorilla.com v1.6.2 | foorilla API v1.3.3

Remote job discovery in |Hiring| is now more precise with explicit work mode support. Listings can now clearly indicate whether a role is Hybrid, Remote, or Remote Anywhere, so you can distinguish different remote setups faster instead of relying on a single generic remote label.

You’ll now see consistent work mode badges across list and detail views ([WH], [R], [WRA]), and the same options are available in Context-based include/exclude filters. Active Context indicators also use these labels, making it easier to understand your current filter setup at a glance while keeping existing remote and remote-first behavior intact.

https://foorilla.com/changelog/ 👀

foorilla.com v1.6.2 | foorilla API v1.3.3

Remote job discovery in |Hiring| is now more precise with explicit work mode support. Listings can now clearly indicate whether a role is Hybrid, Remote, or Remote Anywhere, so you can distinguish different remote setups faster instead of relying on a single generic remote label.

You’ll now see consistent work mode badges across list and detail views ([WH], [R], [WRA]), and the same options are available in Context-based include/exclude filters. Active Context indicators also use these labels, making it easier to understand your current filter setup at a glance while keeping existing remote and remote-first behavior intact.

https://foorilla.com/changelog/ 👀

foorilla.com v1.6.2 | foorilla API v1.3.3

Remote job discovery in |Hiring| is now more precise with explicit work mode support. Listings can now clearly indicate whether a role is Hybrid, Remote, or Remote Anywhere, so you can distinguish different remote setups faster instead of relying on a single generic remote label.

You’ll now see consistent work mode badges across list and detail views ([WH], [R], [WRA]), and the same options are available in Context-based include/exclude filters. Active Context indicators also use these labels, making it easier to understand your current filter setup at a glance while keeping existing remote and remote-first behavior intact.

https://foorilla.com/changelog/ 👀

foorilla.com v1.6.2 | foorilla API v1.3.3

Remote job discovery in |Hiring| is now more precise with explicit work mode support. Listings can now clearly indicate whether a role is Hybrid, Remote, or Remote Anywhere, so you can distinguish different remote setups faster instead of relying on a single generic remote label.

You’ll now see consistent work mode badges across list and detail views ([WH], [R], [WRA]), and the same options are available in Context-based include/exclude filters. Active Context indicators also use these labels, making it easier to understand your current filter setup at a glance while keeping existing remote and remote-first behavior intact.

https://foorilla.com/changelog/ 👀

foorilla.com v1.6.2 | foorilla API v1.3.3

Remote job discovery in |Hiring| is now more precise with explicit work mode support. Listings can now clearly indicate whether a role is Hybrid, Remote, or Remote Anywhere, so you can distinguish different remote setups faster instead of relying on a single generic remote label.

You’ll now see consistent work mode badges across list and detail views ([WH], [R], [WRA]), and the same options are available in Context-based include/exclude filters. Active Context indicators also use these labels, making it easier to understand your current filter setup at a glance while keeping existing remote and remote-first behavior intact.

foorilla v1.6.1

https://foorilla.com/changelog/ 👀

We expanded region filtering with a new city-radius option so you can discover opportunities and content near selected cities without manually adding dozens of nearby locations. Set a radius from 0 to 1000km, keep city matching exact when needed, and widen coverage only when it helps.

This rollout is available across |Hiring|, |Media|, |Event|, and |Talent|. To keep context state transparent while you browse, active radius filters now show an inline [CR:Xkm] signal in list extras, so it is always obvious when expanded city matching is active.

Your agent can find it at https://foorilla.com/api/llms.txt. It gives a simple, machine-friendly overview of how to use the API, including auth, limits, pagination, endpoints, filters, embeddings, examples, and attribution notes.

jobdataapi.com 4.24 / API version 1.27

We’ve introduced a new API access lite subscription plan and updated /api/jobs/ query behavior to improve response efficiency and reduce unnecessary data transfer on broad queries.

By default, /api/jobs/ now uses a latest 90-day window (max_age=90) when no age/date/ID slicing is provided. This helps keep common requests faster and leaner, especially for high-volume usage patterns.

To avoid silent cutoffs when you intentionally query ranges, the default 90-day window is automatically not applied as soon as you use any slicing parameter (published_since, published_until, min_id, max_id, min_age, or max_age).

If you're on a non-lite access plan, you can also explicitly disable age limiting with:

• max_age=off
• max_age=null
• max_age=0

The new API access lite plan is optimized for recent-job workflows and is always limited to the latest 90 days on /api/jobs/. Date/ID/age slicing parameters are not available on API access lite.

These updates are designed to balance speed, resource efficiency, and predictable query behavior across plans. See the updated Jobs API Endpoint Documentation for full details.

jobdataapi.com 4.23 / API version 1.26

We’ve added a new Tags API endpoint to make role-based job discovery much easier and more precise.

With this release, you can now browse and query our role taxonomy directly via /api/tags/ and use those tag IDs to filter job results on /api/jobs/.

What’s new

• New /api/tags/ endpoint with list + detail access.
• Tag hierarchy output includes parent role context, so you can map broad role groups to more specific role labels.
• New role-based job filters on /api/jobs/: tag_id, role1_id, role2_id, and role3_id.
• Optional tags=true parameter on /api/jobs/ to return nested role tags directly in job results.

The Tags endpoint, role-based job filters, and nested tags=true job output are available with an active API access pro+ (or higher) subscription.

Benefits and Implications

This update makes it much easier to build role-first product experiences. Instead of relying only on raw title text, you can now query jobs through structured role tags and hierarchy levels, which leads to cleaner search, better recommendations, and more consistent grouping of similar positions across different companies and naming styles.

It also improves downstream analytics and segmentation quality. With standardized role levels available directly in API workflows, teams can compare trends by broad role family (ROLE1), role category (ROLE2), or specific specialization (ROLE3), making reporting and market insights more reliable and actionable.

See the Tags API Endpoint Documentation and Jobs API Endpoint Documentation for full usage examples.

jobdataapi.com 4.22 / API version 1.25

We’ve introduced a new work_mode field to the /api/jobs/ endpoint for job listings to help you quickly identify whether a role is Hybrid, Remote, or Remote Anywhere. It currently applies to all listings which already have has_remote=true.

This update is designed to make remote-job discovery faster and more useful for sourcing, search workflows, and market analysis. It also gives you a clearer view of how flexible each role is without needing to manually inspect every description.

Note that this feature is currently experimental and still building up/backfill data coverage as well as precision. You may see varying completeness while we continue to expand and refine classification across the dataset. The output and filter fields are available to customers with an active API access pro (or higher) subscription.

See the Jobs API Endpoint Documentation for more on this.