Get pending workflow changes
POST/api/v1/notifications/manage/get-pending-changes
Returns pending workflow edits in the notification provider’s development configuration. These provider environments do not create separate Travila projects or test/live isolation.
The following access conditions are preserved as declared intent and are not implemented by generated code: Authorized scoped domain action.
Use this in a guide: Welcome a new user with an in-app message
Request
Responses
- 200
Pending changes returned
List pending notification configuration changes in the configured environment.
Section ID: DOC-CP-notifications-api-getPendingChanges#example-notifications-getPendingChanges-request
Request example
{}
Illustrative response shape; omitted default fields and actual outcomes depend on the operation.
Section ID: DOC-CP-notifications-api-getPendingChanges#example-notifications-getPendingChanges-response
Response example
{
"changes": [
{
"changeId": "example_123",
"type": "example",
"entityName": "example",
"entityId": "example_123",
"createdAt": "2026-09-16T12:00:00Z",
"createdBy": "example"
}
],
"totalCount": 1
}
Document ID: DOC-CP-notifications-api-getPendingChanges. Section identities and revisions.
| Section | Stable reference |
|---|---|
| Get pending workflow changes | DOC-CP-notifications-api-getPendingChanges#overview |
| Request | DOC-CP-notifications-api-getPendingChanges#request |
| Responses | DOC-CP-notifications-api-getPendingChanges#responses |