Unified APIs
Does the Apideck Connector API match its OpenAPI spec?
YesAll 10 operations we tested return responses that match Apideck Connector's published OpenAPI spec (last run 1 Nov 2026).
apideck.contract[*]
Spec match
100%
10 of 10 operations
Mismatches
0
distinct findings
First response
0.07s
median of tested calls
Last run
1 Nov
12:46 UTC
Contract vs. published spec
Every tested operation returned a 2xx response whose body matches the spec.
All 10 read operations, with a sandbox key. Portman needed one workaround: the spec's SupportedProperty schema refers to itself (circular $ref), which Portman cannot load yet.
Vendor-reported status · 45 days
45 days agotoday
- API now
- operational
- Incident-free days
- 100%
- API incidents
- 0
- Mean time to resolve
- –
Mirrored from status.apideck.com. Counts incidents tagged to the API component plus untagged, vendor-wide ones.
Test the Apideck Connector API yourself
Portman turns the published spec into contract tests and runs them with Newman.
Star Portman685Portman is open source. A star helps other teams find it.
Questions
- Does the Apideck Connector API match its OpenAPI spec?
- Yes. All 10 operations we tested return responses that match Apideck Connector's published OpenAPI spec (last run 1 Nov 2026).
- Where is the Apideck Connector OpenAPI spec?
- Apideck Connector publishes its OpenAPI description at https://github.com/apideck-libraries/openapi-specs.
- Is the Apideck Connector API down?
- Apideck Connector's status page reported the API as operational at our last check. Over the last 45 days, 100% of days had no API incident, with 0 incidents in total. Live status: https://status.apideck.com.
- How can I contract-test the Apideck Connector API myself?
- Run Portman against the spec: npx @apideck/portman -u https://raw.githubusercontent.com/apideck-libraries/openapi-specs/main/connector.yml --runNewman. Portman generates contract tests for every operation and checks status codes, content types and response schemas.