Communication
Does the Discord API match its OpenAPI spec?
Not tested yetPortman cannot load this spec yet (circular $ref). Vendor-reported status is shown below.
discord.contract[*]
Spec match
–
not testable yet
Mismatches
–
distinct findings
First response
–
median of tested calls
Last run
–
Vendor-reported status · 45 days
45 days agotoday
- API now
- operational
- Incident-free days
- 91.1%
- API incidents
- 3
- Mean time to resolve
- 3h 11m
- degradedIssues establishing voice call31 Oct, 15:26 UTC
- degradedIssues establishing voice calls30 Oct, 15:23 UTC
- degradedIssue / Delay in establishing call connection17 Sep, 18:18 UTC
Mirrored from discordstatus.com. Counts incidents tagged to the API component plus untagged, vendor-wide ones.
Test the Discord 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 Discord API match its OpenAPI spec?
- Not tested yet. Portman cannot load this spec yet (circular $ref). Vendor-reported status is shown below.
- Where is the Discord OpenAPI spec?
- Discord publishes its OpenAPI description at https://github.com/discord/discord-api-spec.
- Is the Discord API down?
- Discord's status page reported the API as operational at our last check. Over the last 45 days, 91.1% of days had no API incident, with 3 incidents in total. Live status: https://discordstatus.com.
- How can I contract-test the Discord API myself?
- Run Portman against the spec: npx @apideck/portman -u https://raw.githubusercontent.com/discord/discord-api-spec/main/specs/openapi.json --runNewman. Portman generates contract tests for every operation and checks status codes, content types and response schemas.