Lists every audit revision for the trigger, newest first.
Backs the trigger-history view. Each revision carries a full snapshot of the trigger row and its bindings at the moment of a mutation, plus the `ChangeReason` that distinguishes a schedule edit from a binding reconcile. Empty for triggers that haven't been mutated since the audit log landed.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The trigger identifier.
uuidThe tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/revisions"[
{
"id": "00000000-0000-0000-0000-000000000000",
"triggerId": "00000000-0000-0000-0000-000000000000",
"version": 0,
"changeReason": "CREATED",
"note": "string",
"kind": "SCHEDULE",
"integrationId": "string",
"integrationConfigId": "00000000-0000-0000-0000-000000000000",
"eventType": "string",
"displayName": "string",
"active": false,
"timeout": 0,
"scheduleFrequency": "DAILY",
"scheduleDay": "sunday",
"scheduleDayOfMonth": "_1",
"scheduleHour": "string",
"scheduleMinute": "string",
"intervalValue": 0,
"intervalUnit": "MINUTES",
"timezone": "string",
"filter": {
"match": "ALL",
"conditions": []
},
"bindings": [
{
"agentId": "string",
"parameterMappings": [],
"outputBindingId": null
}
],
"createdBy": "string",
"createdAt": 0
}
]{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Replays a historical revision onto the live trigger.
Copies the snapshot's mutable fields back onto the trigger, replaces bindings to match, and writes a new `RESTORED` revision pointing at the source revision (audit chain stays linear). Returns the post-restore trigger shape. Immutable fields (`kind`, `integrationId`, `eventType`) must match the snapshot — restoring across a kind change is rejected with 400.
Fetches a single audit revision.
Returns the immutable snapshot stored at the given `revision`. Used by the trigger history pane to drive the diff view and the "Restore from this revision" affordance. Revision rows are append-only, so the response shape is stable for the lifetime of the trigger.