Create a new Signing Key for the account making the request

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://twilio.demo.bump-doc.com/doc/iam_v1/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
"iam_v1 MCP server": {
  "url": "https://twilio.demo.bump-doc.com/doc/iam_v1/mcp"
}
Close
POST /v1/Keys
Account sid auth token

API keys

Create a new Signing Key for the account making the request.

application/x-www-form-urlencoded

Body

  • AccountSid string Required

    The SID of the Account that created the Payments resource.

    Minimum length is 34, maximum length is 34. Format should match the following pattern: ^AC[0-9a-fA-F]{32}$.

  • FriendlyName string

    A descriptive string that you create to describe the resource. It can be up to 64 characters long.

  • KeyType string

    Value is restricted.

  • Policy

    The `Policy` object is a collection that specifies the allowed Twilio permissions for the restricted key. For more information on the permissions available with restricted API keys, refer to the Twilio documentation.

Responses

  • 201 application/json

    Created

    Hide headers attributes Show headers attributes
    • Access-Control-Allow-Origin string

      Specify the origin(s) allowed to access the resource

    • Access-Control-Allow-Methods string

      Specify the HTTP methods allowed when accessing the resource

    • Access-Control-Allow-Headers string

      Specify the headers allowed when accessing the resource

    • Access-Control-Allow-Credentials boolean

      Indicates whether the browser should include credentials

    • Access-Control-Expose-Headers string

      Headers exposed to the client

    Hide response attributes Show response attributes object
    • sid string | null

      The unique string that that we created to identify the NewKey resource. You will use this as the basic-auth user when authenticating to the API.

      Minimum length is 34, maximum length is 34. Format should match the following pattern: ^SK[0-9a-fA-F]{32}$.

    • friendly_name string | null

      The string that you assigned to describe the resource.

    • date_created string(date-time-rfc-2822) | null

      The date and time in GMT that the API Key was created specified in RFC 2822 format.

    • date_updated string(date-time-rfc-2822) | null

      The date and time in GMT that the new API Key was last updated specified in RFC 2822 format.

    • secret string | null

      The secret your application uses to sign Access Tokens and to authenticate to the REST API (you will use this as the basic-auth password). Note that for security reasons, this field is ONLY returned when the API Key is first created.

    • policy object | null

      Collection of allow assertions.
POST /v1/Keys 
curl \
 --request POST 'https://iam.twilio.com/v1/Keys' \
 --user "username:password" \
 --header "Content-Type: application/x-www-form-urlencoded" \
 --data 'FriendlyName=foo&AccountSid=ACaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'
Request examples 
{"FriendlyName" => "foo", "AccountSid" => "ACaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"}
{"FriendlyName" => "foo", "AccountSid" => "ACaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "KeyType" => "restricted", "Policy" => "{\"allow\":[\"/twilio/messaging/messages/read\"]}"}
Response examples (201) 
{
  "sid": "SKaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "friendly_name": "foo",
  "date_created": "Mon, 13 Jun 2016 22:50:08 +0000",
  "date_updated": "Mon, 13 Jun 2016 22:50:08 +0000",
  "secret": "foobar",
  "policy": null
}
{
  "sid": "SKaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "friendly_name": "foo",
  "date_created": "Mon, 13 Jun 2016 22:50:08 +0000",
  "date_updated": "Mon, 13 Jun 2016 22:50:08 +0000",
  "secret": "foobar",
  "policy": {
    "allow": [
      "/twilio/messaging/messages/read"
    ]
  }
}