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

Ashby Openings API

The Openings API from Ashby — 11 operation(s) for openings.

Ashby Openings API is one of 53 APIs that Ashby publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include Openings. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 4 JSON Schemas.

This API exposes 11 operations across 11 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

11 operations 11 paths 0 schemas 11 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://api.ashbyhq.com
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

Ashby Openings API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (BasicAuth). An API key is passed in the header as Ashby-Signature (WebhookSignature). By default, every request must be authenticated.

  • BasicAuth — HTTP Basic Auth. Send your Ashby API key as the username and leave the password blank.
  • WebhookSignature — HMAC-SHA256 signature of the webhook payload, used to verify webhook authenticity.

Paths & Operations 11

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

Openings 11
POST
/opening.info
opening.info
openinginfo body → 200
POST
/opening.list
opening.list
openinglist body → 200
POST
/opening.search
opening.search
openingsearch body → 200
POST
/opening.create
opening.create
openingcreate body → 200
POST
/opening.addJob
opening.addJob
openingaddjob body → 200
POST
/opening.removeJob
opening.removeJob
openingremovejob body → 200
POST
/opening.addLocation
opening.addLocation
openingaddlocation body → 200
POST
/opening.removeLocation
opening.removeLocation
openingremovelocation body → 200
POST
/opening.setOpeningState
opening.setOpeningState
openingsetopeningstate body → 200
POST
/opening.setArchived
opening.setArchived
openingsetarchived body → 200
POST
/opening.update
opening.update
openingupdate body → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ashby-hq-openings-api-openapi.yml Raw ↑

Other APIs Ashby publishes across the network.

Ashby Job Postings Public API
Ashby API Key API
Ashby Application API
Ashby Application Feedback API
Ashby Application Feedback Request API
Ashby Application Form API
Ashby Application Hiring Team Role API
Ashby Approval API
Ashby Approval Definition API
Ashby Archive Reason API
Ashby Assessment API
Ashby Brand API
Where this information came from

This is an independent, third-party profile of Ashby Openings 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.