OVOK DOCS
Get startedOvokSignalsSDKsGuidesAPI referenceDeveloper resources
Signals API - Events

Redeliver events

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

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.

Authorization

headerAuthorizationBearer <JWT>

Query Parameters

status?string

The deliveries to send again: failed (the default), expired, held or delivered.

Value in"failed""delivered""pending""expired""held"
since*string

Only events queued at or after this time. Required, so a replay is always bounded.

subscriberId?string

Only this subscriber's deliveries, by Signals id or clientId. A subscriber may name only itself.

Lengthlength <= 128

Response Body

Queued: how many deliveries will be sent again.

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/redeliver?since=string'
Example Response
{  "queued": 0}

List a delivery's attempts GET

Each POST made for it, oldest first: when, how long, the status code or the error, and the first 2 KB of the answer. ### Through ovok - **Who can call it:** Manager apps, and users whose access policy grants the capabilities. - **Capabilities, all required:** `signals_events:read`. 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.

Redeliver one event POST

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.