Skip to main content
WEBHOOK

Authorizations

Authorization
string
header
required

Your API key, sent in the Authorization header: Authorization: YOUR_API_KEY. A Bearer prefix is also accepted (Authorization: Bearer YOUR_API_KEY). Keys are created in the Upwell dashboard (Account → API keys) and are scoped to one organization.

Body

application/json

Details that are sent over to the webhook

id
string
required

The unique identifier for the event.

createdAt
string<date-time>
required

Timestamp when this record was created in Upwell. It is not the business document date and may be much later when historical data is imported. See createdAt definition.

updatedAt
string<date-time>
required

Timestamp of the record's latest recorded update in Upwell. It is not a shipment event, payment date, or document revision date. See updatedAt definition.

status
string
required

The status of the event (e.g., pending, succeeded, sync_error).

operation
string
required

The operation that triggered the event (e.g., INSERT, UPDATE, DELETE).

trigger
string
required

The trigger that caused the event (e.g., update.remittance.status.sync_error).

payload
object
required

The payload of the event, containing the remittance data.

table
string
required

The name of the table associated with the event (e.g., remittances).

webhookSubscriptionId
string
required

The ID of the webhook subscription that triggered this event.

resourceId
string
required

The ID of the resource affected by the event.

retries
object[]
required

Array of retry attempts for this event.

scheduledAt
string<date-time> | null

Timestamp when the asynchronous job is scheduled to run. It is not a promise of completion at that time. See scheduledAt definition.

processedAt
string<date-time> | null

Timestamp recorded for processing the event or job. It is separate from the event's underlying business date. See processedAt definition.

retryOfId
string | null

The ID of the event this is a retry of, if applicable.

Response

200

Return a 200 status to indicate that the data was received successfully