Create a new Signing Key for the account making the request

POST /2010-04-01/Accounts/{AccountSid}/SigningKeys.json

Create a new signing key

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

Path parameters

  • AccountSid string Required

    The SID of the Account that will be responsible for the new Key resource.

Body

  • FriendlyName string

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

Responses

  • 201

    Created

    Hide response attributes Show response attributes object
    • date_created string(date-time-rfc-2822) | null

      The RFC 2822 date and time in GMT that the resource was created

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

      The RFC 2822 date and time in GMT that the resource was last updated

    • friendly_name string | null

      The string that you assigned to describe the resource

    • secret string | null

      The secret your application uses to sign Access Tokens and to authenticate to the REST API.

    • sid string | null

      The unique string that identifies the resource

      Minimum length is 34, maximum length is 34. Format should match the following pattern: ^SK[0-9a-fA-F]{32}$.
POST /2010-04-01/Accounts/{AccountSid}/SigningKeys.json 
curl \
 -X POST https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/SigningKeys.json \
 --user "username:password" \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -d 'FriendlyName=string'
Request example 
{
  "FriendlyName": "string"
}
Request examples 
{
  "FriendlyName": "string"
}
Response examples (201) 
{
  "date_created": "string",
  "date_updated": "string",
  "friendly_name": "string",
  "secret": "string",
  "sid": "string"
}
Response examples (201) 
{
  "date_created": "string",
  "date_updated": "string",
  "friendly_name": "string",
  "secret": "string",
  "sid": "string"
}