Rate this page:

The structure of Twilio’s OpenAPI Spec

Upon visiting either the JSON or YAML folders of twilio-oai/spec, you’ll notice a long list of files instead of a single specification. This is because Twilio’s API spans multiple subdomains, such as,,, and many others.

Each file corresponds to one of these subdomains, which can be determined by looking at the servers property of any of the described endpoint paths in a given file.

For example, in twilio_acounts_v1.json, you’ll find the following top-level property:

  "servers": [
      "url": ""

This indicates that the file corresponds to the subdomain. This same process can be applied to all spec files.

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Community Forums or browsing the Twilio tag on Stack Overflow.


        Thank you for your feedback!

        We are always striving to improve our documentation quality, and your feedback is valuable to us. Please select the reason(s) for your feedback or provide additional information about how we can improve:

        Sending your feedback...
        🎉 Thank you for your feedback!
        Something went wrong. Please try again.

        Thanks for your feedback!

        Refer us and get $10 in 3 simple steps!

        Step 1

        Get link

        Get a free personal referral link here

        Step 2

        Give $10

        Your user signs up and upgrade using link

        Step 3

        Get $10

        1,250 free SMSes
        OR 1,000 free voice mins
        OR 12,000 chats
        OR more