DeleteVoiceConnectorTerminationCredentials - Amazon Chime SDK


Deletes the specified SIP credentials used by your equipment to authenticate during call termination.


This API is is no longer supported and will not be updated. We recommend using the latest version, DeleteVoiceConnectorTerminationCredentials, in the Amazon Chime SDK.

Using the latest version requires migrating to a dedicated namespace. For more information, refer to Migrating from the Amazon Chime namespace in the Amazon Chime SDK Developer Guide.

Request Syntax

POST /voice-connectors/voiceConnectorId/termination/credentials?operation=delete HTTP/1.1 Content-type: application/json { "Usernames": [ "string" ] }

URI Request Parameters

The request uses the following URI parameters.


The Amazon Chime Voice Connector ID.

Pattern: .*\S.*

Required: Yes

Request Body

The request accepts the following data in JSON format.


The RFC2617 compliant username associated with the SIP credentials, in US-ASCII format.

Type: Array of strings

Required: Yes

Response Syntax

HTTP/1.1 204

Response Elements

If the action is successful, the service sends back an HTTP 204 response with an empty HTTP body.


For information about the errors that are common to all actions, see Common Errors.


The input parameters don't match the service's restrictions.

HTTP Status Code: 400


The client is permanently forbidden from making the request.

HTTP Status Code: 403


One or more of the resources in the request does not exist in the system.

HTTP Status Code: 404


The service encountered an unexpected error.

HTTP Status Code: 500


The service is currently unavailable.

HTTP Status Code: 503


The client exceeded its request rate limit.

HTTP Status Code: 429


The client is not currently authorized to make the request.

HTTP Status Code: 401


In the following example or examples, the Authorization header contents( AUTHPARAMS ) must be replaced with an AWS Signature Version 4 signature. For more information about creating these signatures, see Signature Version 4 Signing Process in the AWS General Reference.

You only need to learn how to sign HTTP requests if you intend to manually create them. When you use the AWS Command Line Interface (AWS CLI) or one of the AWS SDKs to make requests to AWS, these tools automatically sign the requests for you with the access key that you specify when you configure the tools. When you use these tools, you don't need to learn how to sign requests yourself.


This example deletes the specified SIP credentials.

Sample Request

POST /voice-connectors/abcdef1ghij2klmno3pqr4/termination/credentials?operation=delete HTTP/1.1 Host: Accept-Encoding: identity User-Agent: aws-cli/1.16.170 Python/3.6.0 Windows/10 botocore/1.12.160 X-Amz-Date: 20190823T184644Z Authorization: AUTHPARAMS Content-Length: 27 {"Usernames": ["jdoe"]}

Sample Response

HTTP/1.1 204 No Content x-amzn-RequestId: a5b5b585-3bd1-44fe-9adc-e15b8a0ec39a Content-Type: application/json Date: Fri, 23 Aug 2019 18:46:44 GMT Connection: keep-alive

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: