OVOK DOCS
Get startedOvokSignalsSDKsGuidesAPI referenceDeveloper resources
Signals API - Events

Redeliver one event

  • Sandbox: available
  • Staging: available
  • Production: unknown
POST
/v1/signals/api/events/{id}/redeliver

Queues this delivery to be sent now, whatever its status, with a fresh retry ladder: the same webhook-id and a new webhook-timestamp. An alert is sent whatever its age.

Through ovok

  • Who can call it: Manager apps, and users whose access policy grants the capabilities.
  • Capabilities, all required: signals_webhooks:update. Project admins have every capability; client applications get no admin bypass.
  • It can reach any patient of your project without naming one, so it is for callers that reach every patient: project admins, manager or submitter apps, and anyone whose Patient access has no criteria.

Authorization

headerAuthorizationBearer <JWT>

Path Parameters

id*string

The delivery's id, an item's id in GET /api/events.

Response Body

Queued.

application/json
  1. response
queued*number

Deliveries queued to be sent again.

Example Request
curl -X POST 'https://api.sandbox.ovok.com/v1/signals/api/events/string/redeliver'
Example Response
{  "queued": 0}

Redeliver events POST

Queues the oldest 1 000 deliveries in `status` (default `failed`) queued since `since` to be sent again, each with a fresh retry ladder: the same `webhook-id`, so receivers dedupe, and a new `webhook-timestamp`. An alert is sent whatever its age. Deliveries to a disabled endpoint, and ones being sent right now, are skipped. While it answers `queued: 1000`, call it again for the next ones. ### Through ovok - **Who can call it:** Manager apps, and users whose access policy grants the capabilities. - **Capabilities, all required:** `signals_webhooks:update`. Project admins have every capability; client applications get no admin bypass. - It can reach any patient of your project without naming one, so it is for callers that reach every patient: project admins, manager or submitter apps, and anyone whose Patient access has no criteria.

Liveness GET

Unauthenticated, always 200: the HTTP status reports that the process is serving, not that its dependencies are well, because this route gates container liveness. `healthy` is false while the database does not answer (`db.ok`); page on it. ### Through ovok - **Who can call it:** any caller with an ovok access token, or a client id and secret. It needs no capability.