UpdateCampaignOutboundCallConfig - Amazon Connect Outbound Campaigns


Updates OutboundCallConfig for an outbound campaign.

Request Syntax

POST /campaigns/id/outbound-call-config HTTP/1.1 Content-type: application/json { "answerMachineDetectionConfig": { "enableAnswerMachineDetection": boolean }, "connectContactFlowId": "string", "connectSourcePhoneNumber": "string" }

URI Request Parameters

The request uses the following URI parameters.


The identifier of the campaign.

Length Constraints: Minimum length of 0. Maximum length of 256.

Pattern: ^[\S]*$

Required: Yes

Request Body

The request accepts the following data in JSON format.


Information about answering machine detection.

Type: AnswerMachineDetectionConfig object

Required: No


The identifier of the published flow associated with this campaign.

Type: String

Length Constraints: Minimum length of 0. Maximum length of 500.

Required: No


The outbound phone number associated with this campaign. Only ported or claimed Amazon Connect phone numbers are allowed.

Type: String

Length Constraints: Minimum length of 0. Maximum length of 100.

Required: No

Response Syntax

HTTP/1.1 200

Response Elements

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


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


You do not have sufficient access to perform this action.

HTTP Status Code: 403


The request could not be processed because of conflict in the current state of the resource.

HTTP Status Code: 409


This exception occurs when there is an internal failure in the outbound campaigns.

HTTP Status Code: 500


The specified resource does not exist.

HTTP Status Code: 404


The request was denied due to request throttling.

HTTP Status Code: 429


The input fails to satisfy the constraints specified by an AWSservice.

HTTP Status Code: 400

See Also

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