canonical: https://jentic.com/apis/demo.jobsoid.com/jobsoid

# Demo Jobsoid Jobsoid API

Jentic publishes the only available OpenAPI specification for Jobsoid API, keeping it validated and agent-ready. Jobsoid is an applicant tracking system that streamlines sourcing, screening, and hiring inside SMB and mid-market organisations. This API surface exposes job listings and supporting lookup data such as locations, departments, divisions, and functions, making it the right fit for embedding a careers section into a corporate website or syndicating live openings to a job board. Endpoints are read-only and well suited to public careers pages.

## For AI agents

Pull live job listings from a Jobsoid account, plus the locations, departments, divisions, and functions used to filter or render them.

## Scope

Does not handle candidate applications, interview scheduling, offers, or onboarding - use for reading published jobs and recruiting taxonomy lookups only.

## Capabilities

- Fetch the list of currently published jobs via GET `/api/v1/jobs`
- Retrieve a single job's details by id with GET `/api/v1/jobs/{jobId}`
- List all locations defined on the Jobsoid account
- List the departments and divisions used to organise roles
- List the job functions used to categorise openings
- Render a careers page or job board feed without scraping HTML

## Use cases

### Embedded Careers Page

Render a live careers page on a corporate website by calling GET `/api/v1/jobs` to list openings and GET `/api/v1/jobs/{jobId}` for full descriptions. Lookup endpoints for locations, departments, divisions, and functions populate the filters, so the careers page stays in sync with whatever recruiters publish in Jobsoid.

Example prompt: Call GET `/api/v1/jobs`, render a card for each job, and link each card to a detail page that fetches GET `/api/v1/jobs/{jobId}.`

### Job Board Syndication

Push live Jobsoid openings to external job boards or aggregators by polling `/api/v1/jobs` on a schedule and diffing against the previous snapshot. The lookup endpoints supply the structured taxonomy partners typically need for category mapping.

Example prompt: Poll GET `/api/v1/jobs` nightly, compute the diff against the last sync, and POST new jobs to the partner job board's import endpoint.

### Filterable Internal Job Board

Build an internal mobility tool that lets employees filter open roles by location, department, division, and function. The four lookup endpoints feed the filter UI and `/api/v1/jobs` is filtered client-side or via query parameters, giving a structured browsing experience without scraping the public site.

Example prompt: Fetch the four lookup lists once, then call GET `/api/v1/jobs` and group the response by department and location for the UI.

### AI Agent Integration via Jentic

An assistant embedded in a careers chatbot can use Jentic to list current openings and answer questions about specific roles. Because the API is read-only and well-scoped, the agent can chain list and detail calls in one turn to give a concrete answer rather than linking to a search page.

Example prompt: Use Jentic to search for 'list jobsoid jobs', execute GET `/api/v1/jobs`, and follow up with GET `/api/v1/jobs/{jobId}` for the role the user asked about.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/jobs` | List published jobs |
| GET | `/api/v1/jobs/{jobId}` | Get details for a specific job |
| GET | `/api/v1/locations` | List job locations |
| GET | `/api/v1/departments` | List departments |
| GET | `/api/v1/divisions` | List divisions |
| GET | `/api/v1/functions` | List job functions |

## Key resources

- **Jobs** — List published jobs and retrieve full details for a single job
- **Lookups** — Locations, departments, divisions, and functions used to categorise roles

## Why Jentic

- **Setup:** Wiring Jobsoid by hand means reading its recruiting API, building the GET calls for jobs and the location, department, division, and function taxonomies, and parsing each response yourself. Through Jentic you install once, import the Jobsoid API from the API Directory, and your agent calls it, and since the published job endpoints are anonymous there is no credential to configure.
- **Permission scoping:** The Jobsoid operations here are all read-only listings and lookups, so you limit the agent to the operations it needs, such as listing open jobs or reading a single job by id, and it can fetch published postings and taxonomies without any ability to write.
- **Credential handling:** The published Jobsoid job endpoints are anonymous, so no secret is held. Where an account key is ever required, it is stored once, encrypted, by your own Jentic One instance, injected at execution time, and never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list open jobs' or 'look up recruiting departments', and Jentic returns the matching Jobsoid operation with its response schema so the agent renders results without browsing the reference docs.

## Related APIs

- **Greenhouse Harvest API** — Enterprise-grade ATS API with deeper candidate, scorecard, and offer data than Jobsoid.
- **Lever API** — Mid-market ATS with strong candidate sourcing and CRM features.
- **Workable API** — ATS aimed at SMB hiring with similar published-jobs and lookups surface.
- **BambooHR API** — HRIS that often pairs with an ATS for employee onboarding after hire.

## FAQ

### Why is there no official OpenAPI spec for Jobsoid API?

Jobsoid does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Jobsoid API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Jobsoid API use?

The endpoints documented in this spec do not declare a security scheme - they expose published job and lookup data and are intended to be called from public careers integrations. Treat any account-specific endpoints not in the spec as requiring credentials managed in Jobsoid.

### Can I list all open jobs with the Jobsoid API?

Yes. GET `/api/v1/jobs` returns the list of currently published jobs. Use GET `/api/v1/jobs/{jobId}` to retrieve the full description for a specific role when rendering a detail page.

### How do I filter Jobsoid jobs by department or location?

Fetch the lookups from `/api/v1/departments` and `/api/v1/locations` to build your filter UI, then either filter the `/api/v1/jobs` response client-side or pass the relevant ids as query parameters when supported.

### What is the base URL for the Jobsoid API?

The OpenAPI spec uses https://demo.jobsoid.com as the base URL; in production the host is your Jobsoid subdomain (for example https://yourcompany.jobsoid.com). The path layout under `/api/v1` is the same.

### How do I render a Jobsoid careers page through Jentic?

Run `pip install jentic`, search for 'list jobsoid jobs', execute GET `/api/v1/jobs`, then chain GET `/api/v1/jobs/{jobId}` per role. Jentic returns typed responses ready to feed straight into a UI component.

### Can I limit what my agent is allowed to do with the Jobsoid API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Jobsoid operations and credentials your agent can use, so you can allow only the calls it actually needs. The Jobsoid operations here are all read-only, so you might permit listing published jobs with GET `/api/v1/jobs` and reading a single role with GET `/api/v1/jobs/{jobId}`, plus the location, department, division, and function lookups, while leaving everything else off. Every listing and lookup is read-only, so a scoped agent can fetch published postings and taxonomies with no ability to write.