j
Transactional Push API
1
Use the transactional push endpoint to programmatically manage transactional push notification send definitions and send transactional push notifications.
This table lists the use cases that the Transactional Push API supports.
| Supported Use Case | HTTP Verb | URI |
|---|---|---|
| Get push send definitions | GET | /messaging/v1/push/definitions |
| Create a push send definition | POST | /messaging/v1/push/definitions |
| Get details of a push send definition | GET | /messaging/v1/push/definitions/{definitionKey} |
| Update a push send definition | PATCH | /messaging/v1/push/definitions/{definitionKey} |
| Delete a push send definition | DELETE | /messaging/v1/push/definitions/{definitionKey} |
| Send a transactional push notification | POST | /messaging/v1/push/messages/ |
| Retrieve the status of a transactional push notification | GET | /messaging/v1/push/messages/{messageKey} |
Append the operation endpoint addresses to this base URL, replacing {subdomain} with the unique subdomain for your Marketing Cloud Engagement tenant:
https://{subdomain}.rest.marketingcloudapis.com
DID THIS ARTICLE SOLVE YOUR ISSUE?
Let us know so we can improve!
Let us know so we can improve!