List all active stipulations for a creditor application
Retailers and integrations authorized for that retailer can access stipulations regardless of user assignment. Hidden stipulations are excluded. Creditor visibility follows the portal resolver: retailer-originated deals expose submitted documents and requirements available to sign or generating; creditor-owned deals retain their existing visibility. Projection updates after uploads are eventually consistent.
This endpoint never returns file contents or download URLs. Each stipulation can carry two kinds of files, and each is fetched from the document download endpoint using the stipulation's id plus a document ID:
- Generated document — the PDF CreditApp produces from the creditor's document template (for example a
CONTRACTstipulation's contract). It is not listed indocuments; its presence is signalled bygeneratedDocumentAvailable. Download it with the literal document IDgenerated. - Uploaded documents — files a user or integration attached to the stipulation. Each appears in
documentswith its ownid, which is the document ID to download it with whendownloadAvailableis true.
A stipulation whose generatedDocumentAvailable is true and whose documents array is empty therefore does have a downloadable file: the generated one.
| Path Parameters |
|---|
applicationId string — REQUIRED |
creditorId string — REQUIRED |
| Header Parameters |
|---|
X-CreditApp-Creditor-ID uuid |
| Responses | |||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
200The complete list of active stipulations
| |||||||||||||||||||||||||||||||
403Access denied | |||||||||||||||||||||||||||||||
404Application or creditor application not found |