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.
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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgov.bc.ca%2Fjobposting" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgov.bc.ca%2Fjobposting" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the WorkBC Job Posting API by hand means mapping the job-search route and the supporting reference lists for regions, industries, and job types yourself, even though no credential is required. Through Jentic you install once, import WorkBC from the API Directory, and your agent calls it through one consistent path.
Permission scoping
The WorkBC job search takes its filters in the request body rather than a resource id in the path, so limit the agent to the operations it needs, such as searching jobs or listing industries. You choose the operations it may call, so the agent cannot reach anything you have not included.
Credential isolation
This service needs no credential, so none is stored, and Jentic still routes each call through your own Jentic One instance so agent activity is logged consistently.
Intent-based discovery
Agents search Jentic by intent such as 'get bc job postings' or 'list workbc industries', and Jentic returns the matching WorkBC operation with its filter body schema typed so the agent calls the right endpoint without reading the docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
Can I limit what my agent is allowed to do with the WorkBC Job Posting API?
Yes. Because you run Jentic One yourself, you decide which WorkBC operations your agent can call, so you can allow just searching postings with POST /jobs and listing regions, industries, job types, or major projects while leaving out anything else. The job search takes its filters in the request body rather than a resource id in the path, so your rules govern the whole operation set the agent may reach. Since the agent can only invoke the operations you have included, it cannot touch endpoints you leave out.
GET STARTED