PUT /tags-rules/{id}
Creates a tags rule with a specified ID.
Servers
- https://api-sandbox.rebilly.com/organizations/{organizationId}
- https://api.rebilly.com/organizations/{organizationId}
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
id |
String | No |
ID of the rule. |
_links[] |
Array | No |
Related resource links. |
_links[].href |
String | No |
Link URL. |
_links[].rel |
String | No |
Type of link. Valid values:
|
name |
String | Yes |
Name of the rule. |
updatedTime |
String | No |
Date and time when the batch was last updated. |
filter |
String | No |
Filter that determines whether to tag or untag.
This field requires a special format.
Use For more information, see Using filters. |
eventType |
Object | Yes | |
addTags[] |
Array | Yes |
List of tags to add to the customer. |
createdTime |
String | No |
Date and time when the batch was created. |
removeTags[] |
Array | Yes |
List of tags to remove for the customer. |
status |
String | No |
Status of the rule. Valid values:
Default value: "active" |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.