A generic outbound webhook POSTs a signed JSON payload to your own endpoint whenever a subscribed event fires on a project: new feedback, an assignment, a mention, a status or priority change, a resolution, or a report linked to a tracker issue. It’s the delivery path for automation, a custom bridge, or any service uMarker doesn’t integrate with directly.
This page is the developer reference for the payload and its signature. To connect the webhook and route it to a project, see Channels & routing.
For integration work, new_feedback and issue_linked are usually the two you want: they let an external system react to reports arriving and to reports being turned into tracker work.
A UUID identifying this event, stable across every retry. De-duplicate on it.
event
string
The event type: one of the seven above, or test for a test send.
account_id
integer
The owning account’s ID.
project.id
integer
The project’s ID.
project.name
string
The project’s name.
feedback.id
integer
The affected report’s ID.
feedback.status
string
The report’s current status.
feedback.url
string
A dashboard link to open the report.
from
string | null
The previous status. Populated for status_change, and for a resolved event that came from a status change. null on every other event.
to
string | null
The new status, on those same two events. On a priority event it instead holds the new priority (none, low, medium, high, urgent). null on every other event.
timestamp
string
ISO 8601 time the event happened, not the time of the current retry.
For a status_change, from and to carry the transition:
A resolution carries the same pair, but arrives as a resolved event rather than a status_change — from: "in_progress", to: "resolved". The exception is a resolved event raised by marking a pin done, where both are null. On a priority event, to holds the new priority level and from is null.
The payload deliberately carries references, not content: an ID and a link, never the reporter’s words, another tenant’s data, or any credential. Fetch the full report through the REST API or open the dashboard link when you need more.
Every webhook request is signed so your receiver can prove it genuinely came from uMarker and wasn’t altered in flight. The signature is in the X-uMarker-Signature header:
The signature covers the exact bytes of the request body. To verify, recompute the same HMAC and compare.
Read the X-uMarker-Signature header and split it on , into t=… and v1=….
Take the raw, unparsed request body: the exact bytes received. Do not re-serialize the parsed JSON; whitespace or key-order changes will break the match.
Compute HMAC-SHA256 of the string `${t}.${rawBody}` using the channel’s signing secret as the key, and hex-encode it.
Compare your value to v1 using a constant-time comparison. A match proves authenticity and integrity; a mismatch means you reject the request.
Optionally, reject the request if t is far from your current clock (e.g. more than a few minutes) to limit replay.
The secret is a 40-character value minted when the webhook connection is created. It’s encrypted at rest and excluded from the channel’s default serialization, so it can’t ride along in an unrelated response.
It’s returned only to someone who may rotate it: holders of integrations.rotatechannel. Connecting a channel, repointing one and rotating its secret return it in their response to a holder of that permission, and the Integrations list shows it to nobody else — so a role that can connect or repoint a channel but not rotate its secret never reads it. Beyond that, only the two ends (uMarker and your receiver) hold it.
If it leaks, rotate it from the Integrations page. Rotation is a hard cutover: the moment you rotate, deliveries are signed with the new secret and the old one stops validating. Update your receiver with the new secret before the next event fires. See Channels: rotate the signing secret.
Every event delivery is queued, so it never blocks the action that triggered it. Each destination is delivered independently: one failing never affects another, or your email. Send test is the one exception — it runs inside your request so it can hand back the real result.
Bounded retries
A 10-second timeout, then up to three attempts with a 10s and 30s backoff, before the connection is flagged as failing. The next successful send clears the flag.
No redirects
Delivery refuses to follow redirects and resolves IPv4 only, so a public endpoint can’t 302 or slip an unvetted address past the guard at send time.
Public HTTPS only
Endpoints are validated at save time: https only, and the host must resolve to a public address. Private, loopback, and metadata addresses are rejected.
Return a 2xx status promptly to acknowledge a delivery. Anything else (including a 3xx redirect) counts as a failure and is retried; after the retry ceiling, the connection is marked failing in the dashboard until its next successful send.