This endpoint allows you to update an existing Sender.
Updates to from.email require re-verification. If your domain has been authenticated, a new Sender will auto verify on creation. Otherwise, an email will be sent to the from.email.
Partial updates are allowed, but fields that are marked as "required" in the POST (create) endpoint must not be nil if that field is included in the PATCH request.
Bearer <<YOUR_API_KEY_HERE>>The on-behalf-of header allows you to make API calls from a parent account on behalf of the parent's Subusers or customer accounts. You will use the parent account's API key when using this header. When making a call on behalf of a customer account, the property value should be "account-id" followed by the customer account's ID (e.g., on-behalf-of: account-id <account-id>). When making a call on behalf of a Subuser, the property value should be the Subuser's username (e.g., on-behalf-of: <subuser-username>). See On Behalf Of for more information.
The unique identifier of the Sender.
A nickname for the Sender. Not used for sending.
The physical address of the Sender.
Additional Sender address information.
The city of the Sender.
The state of the Sender.
The zipcode of the Sender.
The country of the Sender.
The unique identifier of the Sender.
A nickname for the Sender. Not used for sending.
The physical address of the Sender.
Additional Sender address information.
The city of the Sender.
The state of the Sender.
The zipcode of the Sender.
The country of the Sender.
A boolean flag indicating whether the Sender is verified or not. Only verified Senders can be used to send email.
A boolean flag that is true when the Sender is associated with a campaign in Draft, Scheduled, or In Progress status. You cannot update or delete a locked Sender.
The time the Sender was last updated.
The time the Sender was created.