Agreement Document Content Items

### Return multiple agreement document content records by their entity IDs. **Available to:** All authenticated users **Environments:** Demo, Live **[Rate Limit](/overview/core-concepts/rate-limits):** No endpoint-specific limit Returns several `AgreementDocumentContent` entities in one call. Identify them with the `ids` query parameter — a comma-separated list of integer entity IDs. Each record is a lightweight reference: it carries only its own `id` and the `agreementDocumentId` of the agreement document it belongs to. 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. See [`agreementDocumentItems`](/api/rest-api-endpoints/users/agreement-document-items) for the parent `AgreementDocument` entities, which link the content back to customer applications. To fetch a single record by ID, use [`agreementDocumentContentItem`](/api/rest-api-endpoints/users/agreement-document-content-item). To list the content records for an agreement document, use [`agreementDocumentContentDependents`](/api/rest-api-endpoints/users/agreement-document-content-dependents). **Common Failure Scenarios** - An ID in the list doesn't exist or isn't accessible to the calling user (returns `HTTP 404`). - The access token is missing or invalid (returns `HTTP 401`).