Agreement Document Dependents

### List the agreement documents belonging to one customer application. **Available to:** All authenticated users **Environments:** Demo, Live **[Rate Limit](/overview/core-concepts/rate-limits):** No endpoint-specific limit Returns the `AgreementDocument` entities attached to a single customer application. Identify the application with the `masterid` query parameter (the CustomerApplication entity ID). The response contains one record per agreement prepared for that application. Each record reports the application it belongs to (`customerApplicationId`), the template the document was generated from (`agreementDocumentTemplateId`), and the document's language (`locale`). The `timestamp` field marks when the record was created, and `signedTimestamp` appears once the document has been signed — an unsigned document has no `signedTimestamp`, so you can use this endpoint to check which agreements are still outstanding for an application. The platform creates these records when you call [`prepareAgreementDocuments`](/api/rest-api-endpoints/users/prepare-agreement-documents) for a customer application; you can't create or modify them directly through the API. Pass their IDs to [`signAgreementDocuments`](/api/rest-api-endpoints/users/sign-agreement-documents) as `agreementIds` when the applicant signs, and download the generated PDF with [`getAgreementDocument`](/api/rest-api-endpoints/users/get-agreement-document). <Note> The endpoints that create and populate agreement documents — [`startCustomerApplication`](/api/rest-api-endpoints/users/start-customer-application) and [`prepareAgreementDocuments`](/api/rest-api-endpoints/users/prepare-agreement-documents) — are available on Live only, so you'll typically query these records on the Live environment. </Note> To fetch a single record by its entity ID, use [`agreementDocumentItem`](/api/rest-api-endpoints/users/agreement-document-item). To list the agreement documents for several applications in one call, use [`agreementDocumentLDependents`](/api/rest-api-endpoints/users/agreement-document-l-dependents). **Common Failure Scenarios** - The `masterid` customer application doesn't exist or isn't accessible to the calling user (returns `HTTP 404`). - The access token is missing or invalid (returns `HTTP 401`).