generated: '2026-09-11' method: searched source: https://apis.io/developer/overview versioning: scheme: uri-path current: v1 contract_version: 1.2.1 docs: https://apis.io/developer/overview note: >- Single major version in the path (`/api/v1`). No dated versions, no version header, no published version-support window. The OpenAPI declares an `ApiKeyAuth` scheme that is not enforced in v1, explicitly so metering can arrive without a breaking change. deprecation: policy_url: https://apis.io/developer/deprecation policy_published: true policy_last_modified: '2026-08-21' sunset_header: committed deprecation_header: committed link_rel_deprecation: committed standards: [RFC 8594 Sunset, RFC 9745 Deprecation] notice_periods: - change: Deprecating an endpoint or field in /v1 minimum_notice: 6 months before removal - change: Retiring an entire API version minimum_notice: 12 months, with /v1 and /v2 served in parallel - change: Security-forced removal minimum_notice: as much as is safe — announced immediately, with the reason breaking_change_definition: >- Published and specific: removing an endpoint or a response field, renaming a field or changing its type, making an optional parameter required, narrowing an enum or changing the meaning of a value, changing the default page size or the paging envelope, or moving a resource from an open tier to a gated one. Additive change ships into /v1 without a version bump. note: >- CORRECTED 2026-09-11. This block read "No deprecation policy, no RFC 8594 Sunset/Deprecation header support" and recorded it as "a real gap". A full policy is published at https://apis.io/developer/deprecation (HTTP 200, last modified 2026-08-21) committing to deprecated: true in the contract, Deprecation + Sunset headers, a Link rel="deprecation", a named replacement, and the notice periods above. header_support_is_committed_not_observed: >- The commitment is documented; it cannot be observed, because nothing in the contract is currently deprecated (deprecated_operations is empty) so no response has a Sunset header to carry. Recorded as `committed` rather than `true` on purpose — a promise about future responses is not the same measurement as a header seen on the wire. sla: url: null uptime_target: null published: false status_page: >- https://www.postman.com/api-evangelist/apis-io/monitor/APIs-io-Search---Status~1ef6bc29-9da9-4040-b98b-cef03be1155e status_page_kind: postman-monitor changelog: url: https://apis.io/changelog/ artifact: changelog/apis-io-changelog.yml roadmap: url: https://apis.io/roadmap/ issue_tracker: https://github.com/api-evangelist/roadmap note: >- A public roadmap plus a public request inbox (https://github.com/api-search/inbox) — shipped items move from the roadmap to the changelog. deprecated_operations: [] x-evidence: fetched: '2026-08-10' probes: - url: https://apis.io/changelog/ http_status: 200 - url: https://apis.io/roadmap/ http_status: 200 - url: >- https://www.postman.com/api-evangelist/apis-io/monitor/APIs-io-Search---Status~1ef6bc29-9da9-4040-b98b-cef03be1155e http_status: 200 - url: https://apis.io/developer/change-log/ http_status: 404 note: >- Stale pointer carried in apis.yml — the live changelog is at https://apis.io/changelog/. - url: https://apis.io/developer/versioning/ http_status: 404 note: Stale pointer carried in apis.yml — versioning is documented on /developer/overview.