Agreement Document Content L Dependents

### List the content records belonging to multiple agreement documents. **Available to:** All authenticated users **Environments:** Demo, Live **[Rate Limit](/overview/core-concepts/rate-limits):** No endpoint-specific limit Returns the `AgreementDocumentContent` entities attached to several agreement documents in one call. Identify the documents with the `masterids` query parameter — a comma-separated list of AgreementDocument entity IDs. Each record is a lightweight reference: it carries only its own `id` and the `agreementDocumentId` it belongs to, so you can group the results by parent document. The document bytes themselves are stored securely outside the record and aren't returned by this endpoint. To download a generated PDF, call [`getAgreementDocument`](/api/rest-api-endpoints/users/get-agreement-document) with the parent document's `agreementDocumentId`. Content records are created by the platform as part of the customer application agreement workflow; you can't create or modify them directly through the API. You can find agreement document IDs for your customer applications with [`agreementDocumentLDependents`](/api/rest-api-endpoints/users/agreement-document-l-dependents). To list the content records for a single agreement document, use [`agreementDocumentContentDependents`](/api/rest-api-endpoints/users/agreement-document-content-dependents). To fetch specific records by their entity IDs, use [`agreementDocumentContentItems`](/api/rest-api-endpoints/users/agreement-document-content-items). **Common Failure Scenarios** - A `masterids` agreement document doesn't exist or isn't accessible to the calling user (returns `HTTP 404`). - The access token is missing or invalid (returns `HTTP 401`).