Update signature rule mappings
put
/api/REST/2.0/assets/email/signature/rule/{ruleId}/mappings
for the signature rule specified by the
id
parameter.
All mappings should be included in PUT requests as any missing mappings will be removed with the update.
A maximum of 75000 mappings can be provided.Request
Supported Media Types
- application/json
Path Parameters
-
ruleId(required): integer
Id of the signature rule to update.
The request body defines the details of the signature rule mappings to be updated.
Root Schema : schema
Type:
array
Response
Supported Media Types
- application/json
200 Response
OK.
Root Schema : schema
Type:
Show Source
array
-
Array of:
object EmailSignatureRuleMapping
Title:
EmailSignatureRuleMapping
Nested Schema : EmailSignatureRuleMapping
Type:
object
Title:
Show Source
EmailSignatureRuleMapping
-
matchValue:
string
The value to be used for comparison.
-
senderId:
string
The id of the user that will be used as the sender if the contact's field value matches the match value.
-
type:
string
The asset's type in Eloqua.
400 Response
Bad request. See Status Codes for information about other possible HTTP status codes.
401 Response
Unauthorized. See Status Codes for information about other possible HTTP status codes.
403 Response
Forbidden. See Status Codes for information about other possible HTTP status codes.
404 Response
The requested resource was not found. See Status Codes for information about other possible HTTP status codes.
500 Response
The service has encountered an error. See Status Codes for information about other possible HTTP status codes.