Lists recent deliveries newest first: the event ID (your idempotency key), the sequence, the status (pending, delivered or failed), the attempts made, the last HTTP status and when the next retry is due.
Usage
overlane webhook deliveries webhook-id [--service URL] [--team TENANT_ID]Arguments
| Argument | Required | Description |
|---|---|---|
webhook-id |
yes | The webhook ID from overlane webhook list |
Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--service |
string | no | The service address (default: OVERLANE_SERVICE_URL, then the project’s binding, then the hosted service) | |
--team |
string | no | The team (tenant) to act on (default: the one your token belongs to) |
Examples
overlane webhook deliveries whk_0123456789abcdefBehavior
- Effect:
read(changes nothing). - Needs credentials: yes. Uses the network: yes.
- Supports
--dry-run: no. Accepts--force: no. - Machine-readable description:
overlane schema webhook deliveries.
Result
With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.
{
"type": "object",
"properties": {
"tenantId": {
"type": "string"
},
"deliveries": {
"type": "array",
"items": {
"type": "object",
"properties": {
"eventId": {
"type": "string"
},
"sequence": {
"type": "number"
},
"type": {
"type": "string"
},
"status": {
"type": "string"
},
"attempts": {
"type": "number"
},
"nextAttemptAt": {
"type": [
"string",
"null"
]
},
"lastStatus": {
"type": [
"number",
"null"
]
}
},
"required": [
"eventId",
"sequence",
"type",
"status",
"attempts",
"nextAttemptAt",
"lastStatus"
],
"additionalProperties": false
}
}
},
"required": [
"tenantId",
"deliveries"
],
"additionalProperties": false
}See exit codes for the status the process returns.