Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / HR recruiting / Gov Bc Ca / WorkBC Job Posting API
WorkBC Job Posting API logo

Gov Bc Ca WorkBC Job Posting API

Browse all Gov Bc Ca APIs
✓ Official Vendor SpecHR recruitingRecruiting Atsnone5 EndpointsREST

For Agents

Pull a filtered feed of WorkBC job postings and the supporting reference data (job types, regions, industries, major projects) used to filter them.

Use for: Get all WorkBC job postings in a specific region, List the WorkBC supported industries, List the WorkBC supported job types, Find WorkBC job postings tied to a major BC project

Not supported: Does not accept new job submissions, manage applications, or expose employer dashboards — use for reading WorkBC job postings and their supporting reference data only.

The WorkBC Job Posting API exposes a feed of job postings published on the WorkBC Job Board run by the British Columbia government. It also serves the supporting reference data — major projects, job types, regions, and industries — that callers need to filter the feed sensibly. Job postings are retrieved with POST /jobs and matched against the supplied filters in the request body. The API is intended for partners syndicating BC public-sector and broader provincial job listings into their own employment portals or analytics pipelines.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the WorkBC Job Posting API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WorkBC Job Posting API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with WorkBC Job Posting API.

Pull a filtered feed of WorkBC job postings by region, industry, or job type

List the regions used to classify WorkBC job postings

List the job types (full-time, part-time, contract, etc.) supported by WorkBC

List the industries used to classify WorkBC postings

List the major BC projects associated with eligible postings

Syndicate WorkBC postings into an external job portal

Sample WorkBC postings for labour-market analytics

Use Cases

Patterns agents use WorkBC Job Posting API for, with concrete tasks.

★ Job Board Syndication

Mirror WorkBC postings on a partner job board so candidates see provincial opportunities alongside private-sector listings. POST /jobs accepts a filter body and returns matching postings, while GET /regions, GET /Industries, and GET /jobTypes provide the lookup tables needed to populate filters in the partner UI. End-to-end syndication can be running in a day.

Pull WorkBC postings filtered to the Vancouver Island region and return the title, employer, and posting URL for each.

Labour Market Analytics

Sample WorkBC postings periodically to track demand by industry and region across British Columbia. Combine the /jobs feed with the industry, region, and job-type lookups to attribute each posting to a normalised classification. The result is a reproducible dataset for labour-market dashboards without scraping the public site.

Fetch WorkBC postings filtered by the Construction industry and return a count of postings per region.

Major Projects Outreach

Surface employment opportunities tied to BC major capital and infrastructure projects. GET /majorProjects lists the projects and POST /jobs can be filtered by project so workforce-development partners can route candidates to roles connected to specific projects (such as transit expansion or hospital builds).

List WorkBC major projects and return the names and IDs of projects that currently have associated job postings.

AI Agent Job Recommender

An AI career assistant built on Jentic asks the user about their region, industry, and desired job type, then queries WorkBC for matching postings. The agent searches Jentic for 'get bc job postings', loads POST /jobs, and returns curated postings to the user without requiring credentials or web scraping.

Use Jentic to search 'get bc job postings' and pull WorkBC postings filtered to industry 'Health Care' in the Lower Mainland region.

Key Endpoints

5 endpoints — the workbc job posting api exposes a feed of job postings published on the workbc job board run by the british columbia government.

METHOD

PATH

DESCRIPTION

POST

/jobs

Pull a filtered batch of WorkBC job postings

GET

/regions

List BC regions used to filter postings

GET

/Industries

List industries used to classify postings

GET

/jobTypes

List job types used to filter postings

GET

/majorProjects

List major BC projects associated with postings

POST

/jobs

Pull a filtered batch of WorkBC job postings

GET

/regions

List BC regions used to filter postings

GET

/Industries

List industries used to classify postings

GET

/jobTypes

List job types used to filter postings

GET

/majorProjects

List major BC projects associated with postings

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential management

Credential isolation

No credentials are required. Jentic still routes calls through its policy layer so audit logs of WorkBC pulls are preserved even though no secret is injected.

Intent-based discovery

Intent-based discovery

Agents search by intent (e.g., 'get bc job postings' or 'list workbc industries') and Jentic returns the matching operation with the required filter body schema typed.

Time to first call

Time to first call

Direct integration: a few hours to model the filter body and the supporting reference lookups. Through Jentic: under 30 minutes to a working filtered job-posting pull.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Adzuna API

→

Adzuna offers global job search across many countries and aggregators

Choose Adzuna when broader, global job-board coverage matters more than BC-government-managed postings

Alternative

ZipRecruiter API

→

ZipRecruiter exposes job postings across the United States

Choose ZipRecruiter when the user is searching US listings rather than BC government-managed postings

Complementary

BC Data Catalogue API

→

Use the BC Data Catalogue to discover related labour-market datasets

Pair when an analytics workflow needs supporting BC datasets alongside the WorkBC feed

FAQs

Specific to using WorkBC Job Posting API through Jentic.

What authentication does the WorkBC Job Posting API use?

The OpenAPI spec defines no security schemes for this service, so requests are made anonymously over HTTPS. No bearer token or API key is required, and Jentic relays calls as-is without injecting credentials.

Can I filter WorkBC postings by region and industry?

Yes. POST /jobs accepts a filter body that supports region and industry constraints, validated against the lists returned by GET /regions and GET /Industries. Combine with GET /jobTypes and GET /majorProjects for additional facets.

What are the rate limits for the WorkBC Job Posting API?

Specific limits are not declared in the OpenAPI spec. Treat the feed as a batch source: pull periodically rather than per user request, and cache the regions, industries, job types, and major projects lookups since they change infrequently.

How do I pull WorkBC postings through Jentic?

Search Jentic for 'get bc job postings', load the POST /jobs operation, and execute with the desired region and industry filters in the request body. With pip install jentic, the call returns the matching postings ready for syndication or analytics.

Why is /jobs a POST instead of a GET?

The endpoint accepts a structured filter body, which is awkward to express in a GET query string. The spec models it as POST /jobs accordingly so callers can pass nested filters cleanly.

GET STARTED

Start building with WorkBC Job Posting API

Explore with Jentic
View OpenAPI Document