Autopay · OpenAPI Overlay 1.0.0

API Evangelist enhancements for Autopay Accounting Booking API

14 actions 14 updates documentation extends ../openapi/autopay-booking-api-openapi.yml
Derived by API Evangelist Built from the contracts Autopay publishes. Autopay did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

operationIdx-docs400401403500x-api-evangelist-sourcex-api-evangelist-note

Targets 14

$.info
$
$.paths['/booking/v3/permit_definitions'].get
$.paths['/booking/v3/permit_definitions'].get.responses
$.paths['/booking/v3/availability'].get
$.paths['/booking/v3/availability'].get.responses
$.paths['/booking/v3/{id}/status'].get
$.paths['/booking/v3/{id}/status'].get.responses
$.paths['/booking/v3/'].post
$.paths['/booking/v3/'].post.responses
$.paths['/booking/v3/{id}'].put
$.paths['/booking/v3/{id}'].put.responses
$.paths['/booking/v3/{id}'].delete
$.paths['/booking/v3/{id}'].delete.responses

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for Autopay Accounting Booking API
  version: 1.0.0
extends: ../openapi/autopay-booking-api-openapi.yml
x-generated: '2026-09-06'
x-method: generated
x-source: openapi/autopay-booking-api-openapi.yml + https://developer.autopay.io/booking_api/
x-note: 'Non-destructive record of what API Evangelist added on top of the harvested contract: stable
  operationIds (Autopay declares none), the documented 4xx/5xx responses (the contract carries only 200),
  and the cross-cutting semantics published as prose. The underlying OpenAPI is never mutated.'
actions:
- target: $.info
  description: Link the operation surface back to the provider reference page it was read from.
  update:
    x-api-evangelist-source: https://developer.autopay.io/booking_api/
    x-api-evangelist-note: Autopay publishes no OpenAPI. This document is API Evangelist’s reading of
      the HTML reference at the URL above.
- target: $
  description: Declare the runtime semantics Autopay documents in prose but does not express in the contract.
  update:
    x-error-envelope:
      shape: '{ "error_id": string, "message": string, "description"?: string }'
      rfc9457: false
      catalog: errors/autopay-problem-types.yml
    x-idempotency:
      coverage: none
      note: Autopay publishes no idempotency key on any write operation.
    x-rate-limit-headers: []
    x-conventions: conventions/autopay-conventions.yml
    x-lifecycle: lifecycle/autopay-lifecycle.yml
- target: $.paths['/booking/v3/permit_definitions'].get
  description: Add a stable operationId and the reference URL for GET /booking/v3/permit_definitions.
  update:
    operationId: get_v3_permit_definitions
    x-docs: https://developer.autopay.io/booking_api/
- target: $.paths['/booking/v3/permit_definitions'].get.responses
  description: Record the documented error responses, which the harvested contract does not carry.
  update:
    '400':
      description: Bad request. Body is the Autopay error envelope; branch on error_id. See errors/autopay-problem-types.yml.
    '401':
      description: No access token present in header, or the token is invalid. error_id authentication_error.
    '403':
      description: Token lacks the scope or operator context for this API. error_id forbidden.
    '500':
      description: error_id internal_server_error.
- target: $.paths['/booking/v3/availability'].get
  description: Add a stable operationId and the reference URL for GET /booking/v3/availability.
  update:
    operationId: get_v3_availability
    x-docs: https://developer.autopay.io/booking_api/
- target: $.paths['/booking/v3/availability'].get.responses
  description: Record the documented error responses, which the harvested contract does not carry.
  update:
    '400':
      description: Bad request. Body is the Autopay error envelope; branch on error_id. See errors/autopay-problem-types.yml.
    '401':
      description: No access token present in header, or the token is invalid. error_id authentication_error.
    '403':
      description: Token lacks the scope or operator context for this API. error_id forbidden.
    '500':
      description: error_id internal_server_error.
- target: $.paths['/booking/v3/{id}/status'].get
  description: Add a stable operationId and the reference URL for GET /booking/v3/{id}/status.
  update:
    operationId: get_v3_status
    x-docs: https://developer.autopay.io/booking_api/
- target: $.paths['/booking/v3/{id}/status'].get.responses
  description: Record the documented error responses, which the harvested contract does not carry.
  update:
    '400':
      description: Bad request. Body is the Autopay error envelope; branch on error_id. See errors/autopay-problem-types.yml.
    '401':
      description: No access token present in header, or the token is invalid. error_id authentication_error.
    '403':
      description: Token lacks the scope or operator context for this API. error_id forbidden.
    '500':
      description: error_id internal_server_error.
- target: $.paths['/booking/v3/'].post
  description: Add a stable operationId and the reference URL for POST /booking/v3/.
  update:
    operationId: post_v3
    x-docs: https://developer.autopay.io/booking_api/
- target: $.paths['/booking/v3/'].post.responses
  description: Record the documented error responses, which the harvested contract does not carry.
  update:
    '400':
      description: Bad request. Body is the Autopay error envelope; branch on error_id. See errors/autopay-problem-types.yml.
    '401':
      description: No access token present in header, or the token is invalid. error_id authentication_error.
    '403':
      description: Token lacks the scope or operator context for this API. error_id forbidden.
    '500':
      description: error_id internal_server_error.
- target: $.paths['/booking/v3/{id}'].put
  description: Add a stable operationId and the reference URL for PUT /booking/v3/{id}.
  update:
    operationId: put_v3
    x-docs: https://developer.autopay.io/booking_api/
- target: $.paths['/booking/v3/{id}'].put.responses
  description: Record the documented error responses, which the harvested contract does not carry.
  update:
    '400':
      description: Bad request. Body is the Autopay error envelope; branch on error_id. See errors/autopay-problem-types.yml.
    '401':
      description: No access token present in header, or the token is invalid. error_id authentication_error.
    '403':
      description: Token lacks the scope or operator context for this API. error_id forbidden.
    '500':
      description: error_id internal_server_error.
- target: $.paths['/booking/v3/{id}'].delete
  description: Add a stable operationId and the reference URL for DELETE /booking/v3/{id}.
  update:
    operationId: delete_v3
    x-docs: https://developer.autopay.io/booking_api/
- target: $.paths['/booking/v3/{id}'].delete.responses
  description: Record the documented error responses, which the harvested contract does not carry.
  update:
    '400':
      description: Bad request. Body is the Autopay error envelope; branch on error_id. See errors/autopay-problem-types.yml.
    '401':
      description: No access token present in header, or the token is invalid. error_id authentication_error.
    '403':
      description: Token lacks the scope or operator context for this API. error_id forbidden.
    '500':
      description: error_id internal_server_error.

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • 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.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/autopay-booking-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

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.

A second provider on the same verified email joins the account you already have.