CreateConfigurationSet - Amazon Pinpoint Email Service


Create a configuration set. Configuration sets are groups of rules that you can apply to the emails you send using Amazon Pinpoint. You apply a configuration set to an email by including a reference to the configuration set in the headers of the email. When you apply a configuration set to an email, all of the rules in that configuration set are applied to the email.

Request Syntax

POST /v1/email/configuration-sets HTTP/1.1 Content-type: application/json { "ConfigurationSetName": "string", "DeliveryOptions": { "SendingPoolName": "string", "TlsPolicy": "string" }, "ReputationOptions": { "LastFreshStart": number, "ReputationMetricsEnabled": boolean }, "SendingOptions": { "SendingEnabled": boolean }, "Tags": [ { "Key": "string", "Value": "string" } ], "TrackingOptions": { "CustomRedirectDomain": "string" } }

URI Request Parameters

The request does not use any URI parameters.

Request Body

The request accepts the following data in JSON format.


The name of the configuration set.

Type: String

Required: Yes


An object that defines the dedicated IP pool that is used to send emails that you send using the configuration set.

Type: DeliveryOptions object

Required: No


An object that defines whether or not Amazon Pinpoint collects reputation metrics for the emails that you send that use the configuration set.

Type: ReputationOptions object

Required: No


An object that defines whether or not Amazon Pinpoint can send email that you send using the configuration set.

Type: SendingOptions object

Required: No


An array of objects that define the tags (keys and values) that you want to associate with the configuration set.

Type: Array of Tag objects

Required: No


An object that defines the open and click tracking options for emails that you send using the configuration set.

Type: TrackingOptions object

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.


The resource specified in your request already exists.

HTTP Status Code: 400


The input you provided is invalid.

HTTP Status Code: 400


The resource is being modified by another operation or thread.

HTTP Status Code: 500


There are too many instances of the specified resource type.

HTTP Status Code: 400


The resource you attempted to access doesn't exist.

HTTP Status Code: 404


Too many requests have been made to the operation.

HTTP Status Code: 429

See Also

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