design.rejected
Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”When this attempt was sent, in Unix seconds.
When this attempt was sent, in Unix seconds.
v1= followed by the hex HMAC-SHA256, keyed with the endpoint’s signing secret, of the x-pixonaut-timestamp value, a ., and the raw request body.
v1= followed by the hex HMAC-SHA256, keyed with the endpoint’s signing secret, of the x-pixonaut-timestamp value, a ., and the raw request body.
Request Body
Section titled “Request Body”object
The automation that caused the event, beside via.
object
The automation’s id.
What the automation was called when it acted.
When the event happened, in milliseconds since the Unix epoch.
The event’s id. A retry or a redelivery carries the same id, so a receiver can drop one it has already handled.
object
Why the design was rejected, as its decider said, or null when they said nothing. Absent only on an event recorded before rejections carried it.
The design’s revision the decision was made about, as the design read’s revision says it. Absent only on an event recorded before decisions carried it.
automation when one of your automations caused the event; absent otherwise.
Examples
Example
{ "createdAt": 1790000740000, "id": "1790000740000-ce3efd7e-0d97-423d-8b19-6486c99641bd", "payload": { "designId": "6f1c8a2b-3d4e-4f5a-8b6c-7d8e9f0a1b2c", "reason": "The photo is too blurry to print at this size.", "revision": 1 }, "type": "design.rejected"}Responses
Section titled “Responses”Any 2xx acknowledges the delivery.
Questions? Write to [email protected].