> ## Documentation Index > Fetch the complete documentation index at: https://docs.trdrs.co/llms.txt > Use this file to discover all available pages before exploring further. # List webhook deliveries > Returns the delivery log for one endpoint, newest first: what we sent, what your endpoint answered, and what is still queued. Each row carries the exact payload, so an event your receiver dropped can be replayed from here rather than lost. `pending` means the delivery is still inside its retry schedule; `failed` means the schedule was exhausted and we stopped. Terminal rows age out after 60 days; a pending row is never swept. ## OpenAPI ````yaml /partner-platform/openapi.json get /api/partner/webhooks/deliveries openapi: 3.1.0 info: title: trdrs Engine API version: 1.1.0 description: >- ## API Reference This is the served OpenAPI contract for the trdrs engine: market data, trading and account routes for your firm's traders, trdrs Connect account-registration handoff, and preview challenge routes. See Quick Start for the first integration path: key setup, market config, chart data, Connect account registrations, idempotency, stream reconnects, and conformance. See Overview and API Standards for the cross-cutting contract rules. servers: - url: https://app.trdrs.co description: Production - url: / description: This engine security: [] tags: - name: Market data description: >- Symbol search and resolution, OHLCV history, quote snapshots, the server clock, and the live bar stream. Crypto rides each venue’s public feed; futures stream from the caller’s own connected Rithmic account. With none connected, futures requests answer 503 `feed_requires_connection`. - name: News description: >- Aggregated market news and the economic calendar, from licensed/open sources, keyword-tagged with futures roots at ingest. Platform-wide content (nothing per-user), admitted exactly like Market data: a licensed origin, a session, or a firm API key. Headlines page by published time, scope by instrument root, and stream live over SSE; thumbnails serve through the image proxy. - name: Trading description: >- The money surface: entries, exits, replaces, cancels, and position/account flattening. Every order-placing call uses `clientOrderId` as its idempotency key. - name: Account description: >- Reading a connected account. You do not create trading accounts here: a trader connects their own broker account (or creates a free demo account) in the app, and firms create evaluation accounts through the Partner API (Firm accounts → Create evaluation accounts) or register venue accounts through Connect (Create an account registration). Account state and the durable ledgers: balances, positions, working orders, fills, P&L history, and the live account stream. - name: Connect description: >- trdrs Connect account registration, for partner firms. Register an account you issued on your own venue — a pending account registration — with the trader’s sign-in email, optionally the venue account id and the login name your venue issued. The trader finds it waiting in the connect flow the moment they sign in with that email: the connect step is pre-filled with everything except the credential, which the trader always enters themselves. A registration never transmits a password and never grants access to anything before the trader’s own login succeeds. These routes answer a partner-scoped key only; a firm API key or a user session gets 401. Registrations expire after 30 days; re-registering the same email + account refreshes the expiry instead of duplicating. The end-to-end flow guide is **[Quick Start](/docs/guides/quick-start)**. - name: Firm accounts description: >- Evaluation accounts your firm issues on the trdrs venue, through your partner key — the other half of account setup. Connect registrations hand off accounts that exist on your venue; these routes create and manage accounts on ours: the trader trades them on trdrs, and your firm owns the lifecycle. Every route is scoped to accounts your firm created through this API — an account the same trader opened themselves is invisible and untouchable here, by construction. Creation is batched with per-item results, and every write carries your own `referenceId`, so a crashed pipeline retries safely. Served when the deployment runs the prop engine; without it, every route in this group answers `404`. - name: Webhooks description: >- The outbound event bus: register an https endpoint and the platform pushes events to it instead of your back office polling us. Every delivery is signed (`trdrs-signature: t=,v1=` over `${t}.${rawBody}`) so you can prove it came from us and is fresh, and every delivery is durable — a failed attempt is retried with backoff for about nine hours and the whole log is readable, so an endpoint that was down is a delay rather than a lost event. Serves brokers and prop firms alike: the account-registration (`registration.*`) events fire wherever Connect does, and the account events fire where the prop engine runs. - name: Challenges description: >- The prop evaluation surface: challenge programs and a trader’s own enrollments. **Preview: the one group on this page outside the additive-only guarantee** (the pre-contract v1 scaffold; the Phase-1 rebuild will change these shapes; see Stability). **Cookie-authenticated, not key-authenticated**, and served only when the engine runs with `CHALLENGES_ENABLED`; without that flag the bundle is absent and every route below returns `404`. The firm-console/admin half of this surface is deliberately not documented here. It is back office, not licensed surface. paths: /api/partner/webhooks/deliveries: get: tags: - Webhooks summary: List webhook deliveries description: >- Returns the delivery log for one endpoint, newest first: what we sent, what your endpoint answered, and what is still queued. Each row carries the exact payload, so an event your receiver dropped can be replayed from here rather than lost. `pending` means the delivery is still inside its retry schedule; `failed` means the schedule was exhausted and we stopped. Terminal rows age out after 60 days; a pending row is never swept. parameters: - name: id in: query required: true schema: type: string description: The webhook id whose log you want. - name: limit in: query schema: type: integer default: 50 minimum: 1 maximum: 200 description: Rows to return (1–200). Out of range is a 400, never a silent clamp. responses: '200': description: The delivery log (PartnerWebhookDeliveriesResponse) content: application/json: schema: $ref: '#/components/schemas/PartnerWebhookDeliveriesResponse' '400': description: '`id` is missing, or `limit` is outside 1–200' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: The bearer is not a partner-scoped key for an active partner firm content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: >- No webhook with that id belongs to your firm (or webhooks are not enabled here) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - partnerKey: [] x-codeSamples: - lang: javascript label: TypeScript source: >- const res = await fetch('https://app.trdrs.co/api/partner/webhooks/deliveries?id=whk_4d19c2&limit=20', { headers: { Authorization: `Bearer ${process.env.TRDRS_API_KEY}` }, }) const data = await res.json() - lang: shell label: cURL source: >- curl 'https://app.trdrs.co/api/partner/webhooks/deliveries?id=whk_4d19c2&limit=20' \ -H "Authorization: Bearer $TRDRS_API_KEY" components: schemas: PartnerWebhookDeliveriesResponse: type: object description: >- PartnerWebhookDeliveriesResponse. The delivery log for one endpoint, newest first — what we sent, what came back, and what is still queued. properties: deliveries: type: array items: type: object properties: id: type: string eventType: type: string status: type: string enum: - pending - delivered - failed description: >- `pending` is still being retried; `failed` exhausted the retry schedule. attempts: type: integer responseStatus: type: - integer - 'null' lastError: type: - string - 'null' createdAt: type: string format: date-time lastAttemptAt: type: - string - 'null' format: date-time payload: type: object description: >- The exact JSON body we sent (or will send), so a missed event can be replayed from here. required: - id - eventType - status - attempts - responseStatus - lastError - createdAt - lastAttemptAt - payload required: - deliveries example: deliveries: - id: dlv_8a13f0 eventType: risk.locked status: delivered attempts: 1 responseStatus: 200 lastError: null createdAt: '2026-08-24T19:41:07Z' lastAttemptAt: '2026-08-24T19:41:07Z' payload: type: risk.locked createdAt: '2026-08-24T19:41:07Z' data: accountNumber: EVAL-7C21A9 reason: eval_breach - id: dlv_8a13ef eventType: balance.recorded status: pending attempts: 2 responseStatus: 502 lastError: HTTP 502 createdAt: '2026-08-24T19:12:44Z' lastAttemptAt: '2026-08-24T19:18:02Z' payload: type: balance.recorded createdAt: '2026-08-24T19:12:44Z' data: accountNumber: EVAL-7C21A9 op: debit amount: 800 referenceId: payout-2026-08-31-a ErrorResponse: type: object properties: error: type: string required: - error example: error: invalid_instrument securitySchemes: partnerKey: type: http scheme: bearer description: >- A partner-scoped API key (`trdrs_sk_…`), issued to a trdrs Connect partner firm and accepted only under `/api/partner/`. Same format as the firm (`tenant`) key, different scope: a firm API key is refused here, and this key is refused everywhere else. ````