Twilio - Api OpenAPI spec score
Octri scored the public spec at https://raw.githubusercontent.com/twilio/twilio-oai/main/spec/json/twilio_api_v2010.json for what a code generator can do with it. This is a reading of the document, not a grade of the API.
197 operations · 150 models · 75 tags · OpenAPI 3.0.1
Scored 22 October 2026 · fingerprint bfdf249a1298… · spec version 1.0.0 · server api.twilio.com
Unchanged since 7 October 2026.
Where the points went
Every rule, heaviest first, with what it cost this document, how much of the surface it touched, and where. The rule id links to what that rule checks.
| Rule | Weight | Result | Surface | Locations |
|---|---|---|---|---|
| Successful responses declare a schemaresponse-schema | 2.0 | 0.4 lost | 1 of 197 operations | GET /2010-04-01/Accounts/{AccountSid}/Recordings/{ReferenceSid}/AddOnResults/{AddOnResultSid}/Payloads/{PayloadSid}/Data.json |
| Shared models live in components and are $ref'dshared-schemas-referenced | 2.0 | 0.4 lost | 2 of 197 operations | memory://audit/openapi.yaml#/paths/~12010-04-01~1Accounts~1{AccountSid}~1Calls~1{CallSid}~1Recordings~1{Sid}.json/postmemory://audit/openapi.yaml#/paths/~12010-04-01~1Accounts~1{Sid}.json/post |
| Generated public names do not collideoperation-id-unique | 2.0 | Clean | 197 operations clean | Nothing found |
| Every path placeholder has a parameterpath-parameters-declared | 1.5 | Clean | 197 operations clean | Nothing found |
| Every operation declares an operationIdoperation-id-present | 1.0 | Clean | 197 operations clean | Nothing found |
| operationIds read as method namesoperation-id-naming | 1.0 | Clean | 197 operations clean | Nothing found |
| Operations carry a summary or descriptionoperation-documented | 1.0 | 0.4 lost | 47 of 197 operations | GET /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers/Mobile.jsonGET /2010-04-01/Accounts/{AccountSid}/Usage/Records/Yearly.jsonGET /2010-04-01/Accounts/{AccountSid}/AvailablePhoneNumbers/{CountryCode}/TollFree.jsonand 44 more |
| Request bodies are documentedrequest-body-documented | 1.0 | 0.3 lost | 23 of 197 operations | POST /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers/Mobile.jsonPOST /2010-04-01/Accounts/{AccountSid}/Messages.jsonPOST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Payments.jsonand 20 more |
| Failure responses are declarederror-responses | 1.0 | 1.0 lost | 195 of 197 operations | GET /2010-04-01/Accounts/{AccountSid}/Usage/Triggers.jsonGET /2010-04-01/Accounts/{AccountSid}/Addresses.jsonGET /2010-04-01/Accounts/{AccountSid}/Usage/Records.jsonand 192 more |
| Operations are taggedoperation-tagged | 1.0 | Clean | 197 operations clean | Nothing found |
| No duplicate or equivalent pathsduplicate-paths | 1.0 | Clean | 121 paths clean | Nothing found |
| Authentication is describedsecurity-declared | 1.0 | Clean | Declared | Nothing found |
| Parameters explain their purposeparameters-documented | 0.75 | 0.17 lost | 7 of 197 operations | DELETE /2010-04-01/Accounts/{AccountSid}/SigningKeys/{Sid}.json#path:SidGET /2010-04-01/Accounts/{AccountSid}/SigningKeys/{Sid}.json#path:SidPOST /2010-04-01/Accounts/{AccountSid}/SigningKeys/{Sid}.json#path:AccountSidand 4 more |
| A server URL is declaredserver-url | 0.5 | Clean | Declared | Nothing found |
What 7.3 means for an SDK
A mixed reading, and the three rules that decide most of it.
The client compiles and works. Callers will feel the soft spots: a few methods that return an untyped value, arguments with no hint on them, a namespace or two named after a path segment rather than a resource.
Three rules carry six of the 10 points between them. On this document they took 0.83.
−0.4
Successful responses declare a schema
1 of 197 operations
−0.4
Shared models live in components and are $ref'd
2 of 197 operations
Clean
Generated public names do not collide
197 operations clean
What to change first
Every rule that deducted, in the order they cost.
0.4 lost
Successful responses declare a schema
Give the success response a schema, or a $ref to one in components. A 204 needs nothing.
Inside Octri this one has a one-click fix.
0.4 lost
Shared models live in components and are $ref'd
Move the shape into components.schemas once and $ref it from each operation that returns or accepts it.
0.4 lost
Operations carry a summary or description
Write one sentence of summary. It lands on the reference page and in the SDK's doc comment.
Inside Octri this one has a one-click fix.
0.3 lost
Request bodies are documented
Describe the body, or the fields inside it. Field-level prose is the one that reaches the SDK's arguments.
Inside Octri this one has a one-click fix.
1.0 lost
Failure responses are declared
Declare the failures you actually return, or one `default` response carrying your error shape.
0.17 lost
Parameters explain their purpose
Describe what the parameter does and what a valid value looks like. One line each.
Inside Octri this one has a one-click fix.
Where to go next
- Score your own spec The same fourteen rules, on any public URL. No account, and the spec is not kept.
- OpenAPI to a TypeScript SDK Published to npm, with the type definitions generated from your spec.
- OpenAPI to an MCP server The same endpoints, as tools an agent can call.
- How SDK Studio shapes a client Naming, hooks and packaging, decided before ten runtimes are built.
The spec at raw.githubusercontent.com is public. Octri keeps the `info` block, the score, and up to five sample finding locations per rule. The document itself is not stored and is not served from here. The audit predicts what an SDK generator can do with the description; it is not a security review, an uptime measurement or a critique of the API’s design. This page is not affiliated with Twilio - Api or Twilio Support.