Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Wellhub Jobs API

Endpoints for managing eligibility batch jobs. A job follows a lifecycle: Create → Add Items → Submit → Monitor.After submission, the job transitions through the following statuses:- `PENDING` — job has been submitted and is queued.- `VALIDATING` — intermediate state while items are being validated.- `SUCCEEDED` — all items processed successfully (terminal).- `SUCCEEDED_WITH_ERRORS` — job has been partially processed, with error entries that must be fixed (terminal). → **Call `GET /errors` to review failures.**- `REJECTED` — job was rejected due to validation issues (terminal). → **Call `GET /errors` to review failures.**- `INTERNAL_SERVER_ERROR` — a server-side error occurred during processing; it is recommended to try again (terminal). → **Retry job submission.**

Wellhub Jobs API is one of 4 APIs that Wellhub publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Jobs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 6 operations across 5 paths, and defines 11 schemas. It is described by OpenAPI 3.0.3, at version v1.0.0.

Requests are made against a single base URL, https://api.clients.wellhub.com.

6 operations 5 paths 11 schemas 3 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v1.0.0
Base URL
https://api.clients.wellhub.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Wellhub Jobs API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (OAuth2).

  • OAuth2 — Bearer token obtained from POST /oauth/token using the clientcredentials grant type.

Paths & Operations 6

Across 5 paths, the API surfaces 6 operations — 3 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Jobs 6

Endpoints for managing eligibility batch jobs. A job follows a lifecycle: Create → Add Items → Submit → Monitor. After submission, the job transitions through the following status…

POST
/v1/eligibility/jobs
Create a new eligibility job
→ 201401403500
GET
/v1/eligibility/jobs/{job-id}/items
List job items
2 params → 200400401403404500
POST
/v1/eligibility/jobs/{job-id}/items
Add items to a job
1 param body → 204400401403404413500
POST
/v1/eligibility/jobs/{job-id}/submit
Submit a job for processing
1 param → 202400401403404409422500
GET
/v1/eligibility/jobs/{job-id}/status
Get job status
1 param → 200400401403404500
GET
/v1/eligibility/jobs/{job-id}/errors
List job errors
2 params → 200400401403500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are JobItemResponse (18 properties), CreateJobItem (14 properties), JobError (6 properties), JobStatusResponse (4 properties). Each schema is shown below with its type and property counts.

Statistics
object
3 properties
MultipleErrorResponse
object
3 properties
CreateJobItem
object
14 properties 2 required
JobItemsResponse
object
2 properties
JobErrorsResponse
object
2 properties
HTTPError
object
2 properties
JobError
object
6 properties
JobItemResponse
object
18 properties
FieldError
object
2 properties
JobStatusResponse
object
4 properties
JobResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wellhub-jobs-api-openapi.yml Raw ↑

Other APIs Wellhub publishes across the network.

Wellhub Companies API
Wellhub Employees API
Wellhub OAuth API