MadHive · OpenAPI Overlay 1.0.0

API Evangelist enhancements for Madhive API

4 actions 4 updates update extends openapi/madhive-api-openapi-original.yml
Authorship not recorded No authorship marker is recorded for this file. It is not presented as the provider's.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-profilex-apievangelist-enrichedx-apievangelist-sourcex-apievangelist-operationsx-apievangelist-artifactsx-apievangelist-observations

Targets 2

$.info
$.tags

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for Madhive API
  version: 1.0.0
extends: openapi/madhive-api-openapi-original.yml
actions:
- target: $.info
  update:
    x-apievangelist-profile: https://apis.io/providers/madhive/
    x-apievangelist-enriched: '2026-08-04'
    x-apievangelist-source: https://developer.madhive.com/
    x-apievangelist-operations: 75
- target: $.info
  update:
    x-apievangelist-artifacts:
      authentication: authentication/madhive-authentication.yml
      conventions: conventions/madhive-conventions.yml
      errors: errors/madhive-problem-types.yml
      lifecycle: lifecycle/madhive-lifecycle.yml
      rate_limits: rate-limits/madhive-rate-limits.yml
      conformance: conformance/madhive-conformance.yml
      data_model: data-model/madhive-data-model.yml
      mcp: mcp/madhive-mcp.yml
      tool_crosswalk: mcp/madhive-tool-crosswalk.yml
- target: $.info
  update:
    x-apievangelist-observations:
      idempotency: not supported — no Idempotency-Key header or parameter is documented
      error_format: proprietary JSON envelope (error/errors/status/transaction); not RFC 9457 application/problem+json
      rate_limit_headers: not documented — per-tier limits are published in the FAQ only
      operations_missing_operation_id:
      - GET /health
      - POST /v1/campaigns/{cid}/lineitems/{id}/activation
- target: $.tags
  update:
  - name: Madhive API
    description: Single tag declared by the provider; every one of the 75 operations carries it, so the spec offers
      no resource-level tag grouping.