Generated by API Evangelist
Written by API Evangelist tooling for Bindbee's API. It is a proposal applied on top of the contract, not a document Bindbee publishes.
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
title: API Evangelist conversational phrasing for Bindbee Reject Reason API
version: 1.0.0
extends: openapi/bindbee-reject-reason-api-openapi.yml
actions:
- target: $.info
update:
x-apievangelist-phrasing:
method: generated
generated: '2026-09-26'
generator: build-phrasing.py
label: Generated by API Evangelist
operations: 3
- target: $.paths['/api/ats/v1/reject-reasons'].get
update:
x-apievangelist-phrasing:
intent: List candidate rejection reasons
effect: read
questions:
- What rejection reasons are configured in the ATS?
- Can I list reject reasons changed recently?
instructions:
- text: List reject reasons modified after {modified_after}.
slots:
modified_after: query.modified_after
- text: Show every candidate rejection reason.
method: generated
generated: '2026-09-26'
- target: $.paths['/api/ats/v1/reject-reasons'].post
update:
x-apievangelist-phrasing:
intent: Add a rejection reason
effect: write
questions:
- How do I add a new rejection reason to the ATS?
- Can I create reject reasons through the unified API?
instructions:
- text: Create a new reject reason in the ATS for connector {connector}.
slots:
connector: header.x-connector-token
- text: Add a candidate rejection reason.
method: generated
generated: '2026-09-26'
- target: $.paths['/api/ats/v1/reject-reasons/{id}'].get
update:
x-apievangelist-phrasing:
intent: Get one rejection reason
effect: read
questions:
- What does a single reject reason record contain?
- Can I fetch one rejection reason by id?
instructions:
- text: Get reject reason {id}.
slots:
id: path.id
- text: Retrieve rejection reason {id} with raw data.
slots:
id: path.id
method: generated
generated: '2026-09-26'
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.