How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Greenhouse JobPosts API

Public-facing job postings and their statuses.

Greenhouse JobPosts API is one of 27 APIs that Greenhouse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Job Posts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, authentication docs, rate-limit docs, and 2 JSON Schemas.

This API exposes 7 operations across 6 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://harvest.greenhouse.io/v1.

7 operations 6 paths 2 schemas 5 GET2 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://harvest.greenhouse.io/v1
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Greenhouse JobPosts API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

  • BasicAuth — HTTP Basic with the Harvest API key as the username and an empty password (Base64 encoded).

Paths & Operations 7

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

JobPosts 7

Public-facing job postings and their statuses.

GET
/job_posts
List Job Posts
listJobPosts 4 params → 2004XX
GET
/job_posts/{id}
Retrieve Job Post
getJobPost 1 param → 2004XX
PATCH
/job_posts/{id}
Update Job Post
updateJobPost 2 params body → 2004XX
GET
/job_posts/{id}/custom_locations
List Job Post Custom Locations
listJobPostCustomLocations 1 param → 2004XX
PATCH
/job_posts/{id}/status
Update Job Post Status
updateJobPostStatus 2 params body → 2004XX
GET
/jobs/{job_id}/job_posts
List Job Posts For Job
listJobJobPosts 1 param → 2004XX
GET
/jobs/{job_id}/job_posts/{id}
Retrieve Job Job Post
getJobJobPost 2 params → 2004XX

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are JobPost (9 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
JobPost
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

greenhouse-io-jobposts-api-openapi.yml Raw ↑

Other APIs Greenhouse publishes across the network.

Greenhouse Recruiting Webhooks
Greenhouse Onboarding Webhooks
Greenhouse ActivityFeed API
Greenhouse Applications API
Greenhouse Approvals API
Greenhouse Auth API
Greenhouse Candidates API
Greenhouse CustomFields API
Greenhouse Departments API
Greenhouse Events API
Greenhouse GraphQL API
Greenhouse JobOpenings API
Where this information came from

This is an independent, third-party profile of Greenhouse JobPosts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.