Bulk retry webhook deliveries
Triggers redeliveries for many failed events in one call. Cross-organisation or non-existent IDs are silently dropped and surfaced in meta.dropped_ids. The system’s per-webhook concurrency limit governs how fast retries fan out — there’s no need to throttle from the client.
Authentication
AuthorizationBearer
OAuth 2.0 Client Credentials Flow. To obtain an access token:
1. Request API credentials from HINDSITE support to receive your `client_id` and `client_secret`
2. Make a POST request to obtain an access token:
```
POST https://app.hindsiteind.com/oauth/token
Content-Type: application/x-www-form-urlencoded
grant_type=client_credentials&client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET
```
3. The response will contain your access token:
```json
{
"access_token": "your_access_token_here",
"token_type": "Bearer",
"expires_in": 7200,
"created_at": 1234567890
}
```
4. Include the token in subsequent API requests:
```
Authorization: Bearer your_access_token_here
```
Request
This endpoint expects an object.
delivery_ids
Delivery IDs to retry. IDs that aren’t in your organisation (or don’t exist) are silently dropped and reported in the response’s meta.dropped_ids.
Response
Created redeliveries with a summary of dropped IDs
webhook_deliveries
meta
Errors
403
Forbidden Error

