Pending documents and who is currently blocking each
Every PENDING document the caller can see (same readable scope as every other document list), with who is currently holding it up — the lowest-order unsigned signer for a sequential document, or every unsigned signer for a parallel one, group-aware. No idle-day threshold is applied: there is no existing product rule for what counts as "stalled" versus merely pending, so this reports the unconditional blocking state and leaves any staleness judgement to the caller.
View as MarkdownAuthorization
bearer In: header
Query Parameters
Page size. Default 10, capped at 100.
Page start. Default 0.
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/documents/waiting"{ "documents": [ { "id": "string", "name": "string", "sentAt": "2019-08-24T14:15:22Z", "waitingOn": [ { "recipientId": "string", "name": "string", "email": "string", "isGroup": true, "viewedAt": "2019-08-24T14:15:22Z", "members": [ { "name": "string", "email": "string", "viewedAt": "2019-08-24T14:15:22Z", "declinedAt": "2019-08-24T14:15:22Z" } ] } ] } ], "total": 0, "limit": 0, "offset": 0}Per-recipient engagement detail for one document
First viewed, signed, time to sign, and who is currently blocking (sequential/parallel/group-aware, reusing the same turn-order logic the signing flow itself uses) — for one document. firstViewedAt is exactly that: the recipient's first open, since the platform never records a repeat view. timeToSignSeconds falls back to sentAt→signedAt when viewedAt is null (e.g. the owner signed this recipient in person), reported via timeToSignBasis ("fromView"|"fromSend") so the two are never silently mixed.
Completion rate and time over a date range
Every sent document the caller can see, optionally narrowed to a sent_at date range (from/to — RFC3339 or YYYY-MM-DD), with a summary (sentCount, completedCount, completionRate, avgCompletionSeconds) computed over the FULL filtered cohort plus the underlying documents for drill-down. completionRate is null (not 0) when sentCount is 0 — an empty period must never render as "0% completion". The cohort is always "documents sent in this window" for both the numerator and denominator; it is never silently swapped to "documents completed in this window" under a different sent_at filter.