Greenhouse Sections API
The Sections API from Greenhouse — 2 operation(s) for sections.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/greenhouse-sections-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Greenhouse Job Board Sections API
description: The Job Board API enables building careers pages with custom look and feel. Read endpoints (GET) require no authentication; submitting an application (POST) requires HTTP Basic Auth with the board's API key.
version: '1.0'
contact:
name: Greenhouse Developer Support
url: https://developers.greenhouse.io/job-board.html
servers:
- url: https://boards-api.greenhouse.io/v1/boards/{board_token}
description: Production
variables:
board_token:
default: example
description: The board token issued by Greenhouse for the organization.
tags:
- name: Sections
paths:
/sections:
get:
tags:
- Sections
summary: List prospect sections
responses:
'200':
description: Prospect sections and postings
/sections/{section_id}:
parameters:
- in: path
name: section_id
required: true
schema:
type: integer
get:
tags:
- Sections
summary: Retrieve prospect section
responses:
'200':
description: Section with prospect posts
components:
securitySchemes:
basicAuth:
type: http
scheme: basic