Ashby · Capability

Ashby — Approvals

Ashby Approval Definitions capability. Programmatically configure approval workflows on API-managed entities.

Ashby — Approvals is a Naftiko capability published by Ashby, one of 19 capabilities the APIs.io network indexes for this provider. It bundles 1 operation across the POST method rooted at /v1/approvalDefinition.update.

The capability includes 1 state-changing operation. Lead operation: Create or update an approval definition. Can be deployed as a REST endpoint, MCP tool, or Agent Skill via Naftiko.

Tagged areas include Ashby, Recruiting, ATS, and Approvals.

Run with Naftiko AshbyRecruitingATSApprovals

What You Can Do

POST
Approval definition update — Create or update an approval definition
/v1/approvalDefinition.update

MCP Tools

ashby-approval-definition-update

Create or update an approval definition

idempotent

Capability Spec

approvals-approvals.yaml Raw ↑ 
naftiko: 1.0.0-alpha2
info:
  label: "Ashby \u2014 Approvals"
  description: Ashby Approval Definitions capability. Programmatically configure approval workflows on API-managed entities.
  tags:
  - Ashby
  - Recruiting
  - ATS
  - Approvals
  created: '2026-05-25'
  modified: '2026-05-25'
binds:
- namespace: env
  keys:
    ASHBY_API_KEY: ASHBY_API_KEY
capability:
  consumes:
  - type: http
    namespace: approvals-approvals
    baseUri: https://api.ashbyhq.com
    description: Ashby Approval Definitions capability. Programmatically configure approval workflows on API-managed entities. Backed by the Ashby public REST API.
    resources:
    - name: approval-definition-update
      path: /approvalDefinition.update
      operations:
      - name: approval-definition-update
        method: POST
        description: Create or update an approval definition
        outputRawFormat: json
        outputParameters:
        - name: result
          type: object
          value: $.
        inputParameters:
        - name: body
          in: body
          type: object
          description: Request body (JSON). See https://developers.ashbyhq.com/reference for the schema of each operation.
          required: false
        headers:
        - name: Accept
          value: application/json; version=1
        - name: Content-Type
          value: application/json
    authentication:
      type: basic
      username: '{{env.ASHBY_API_KEY}}'
      password: ''
      description: 'HTTP Basic Auth: Ashby API key as username, blank password.'
  exposes:
  - type: rest
    namespace: approvals-approvals-rest
    port: 8080
    description: "REST adapter for Ashby \u2014 Approvals. One Spectral-compliant resource per consumed operation, prefixed with /v1."
    resources:
    - path: /v1/approvalDefinition.update
      name: approval-definition-update
      description: REST surface for approval-definition-update.
      operations:
      - method: POST
        name: approval-definition-update
        description: Create or update an approval definition
        call: approvals-approvals.approval-definition-update
        with:
          body: rest.body
        outputParameters:
        - type: object
          mapping: $.
  - type: mcp
    namespace: approvals-approvals-mcp
    port: 9090
    transport: http
    description: "MCP adapter for Ashby \u2014 Approvals. One tool per consumed operation, routed inline through this capability's consumes block."
    tools:
    - name: ashby-approval-definition-update
      description: Create or update an approval definition
      hints:
        readOnly: false
        destructive: false
        idempotent: true
      call: approvals-approvals.approval-definition-update
      with:
        body: tools.body
      outputParameters:
      - type: object
        mapping: $.