> ## Documentation Index > Fetch the complete documentation index at: https://developers.hubspot.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Read journal entries in batch > Fetch up to 100 journal entries by offset in a single request. Offsets that can't be fetched don't fail the request; they're listed in `errors` and counted in `numErrors`. > [accordion] Supported products ## OpenAPI ````yaml specs/2027-03-beta/webhooks-journal-webhooks-journal-v2027-03-beta.json POST /webhooks-journal/journal/2027-03-beta/batch/read openapi: 3.0.1 info: title: Webhooks Journal Webhooks Journal description: Basepom for all HubSpot Projects version: 2027-03-beta x-hubspot-product-tier-requirements: marketing: FREE sales: FREE service: FREE cms: FREE commerce: FREE crmHub: FREE dataHub: FREE servers: - url: https://api.hubapi.com security: [] tags: - name: Advanced - name: Basic - name: Batch paths: /webhooks-journal/journal/2027-03-beta/batch/read: post: tags: - Batch summary: Batch read description: >- Fetch up to 100 journal entries by offset in a single request. Offsets that can't be fetched don't fail the request; they're listed in `errors` and counted in `numErrors`. operationId: >- post-/webhooks-journal/journal/2027-03-beta/batch/read_/webhooks-journal/journal/2027-03-beta/batch/read parameters: - name: installPortalId in: query description: >- An integer representing the ID of the portal installation for which the webhooks journal data should be retrieved. required: false style: form explode: true schema: type: integer format: int32 requestBody: content: application/json: schema: $ref: '#/components/schemas/BatchInputString' required: true responses: '200': description: successful operation content: application/json: schema: $ref: '#/components/schemas/BatchResponseJournalFetchResponse' '207': description: multiple statuses content: application/json: schema: $ref: >- #/components/schemas/BatchResponseJournalFetchResponseWithErrors default: $ref: '#/components/responses/Error' description: '' security: [] components: schemas: BatchInputString: required: - inputs type: object properties: inputs: type: array description: >- The offsets (UUIDs) of the journal entries to fetch, up to 100 per request. Use the `currentOffset` values returned by other journal endpoints. If any value is not a valid UUID, the whole request is rejected with a `400`. Offsets that can't be fetched don't fail the request: each one appears in `errors` with the offset in `context.offset`, and `numErrors` counts them. Offsets with no matching entry for your app (or for `installPortalId` when it is set) have category `OBJECT_NOT_FOUND`; other failures have `INTERNAL_SERVER_ERROR`. An empty list returns an empty result. items: type: string BatchResponseJournalFetchResponse: required: - completedAt - results - startedAt - status type: object properties: completedAt: type: string description: >- The date and time when the batch operation was completed, in ISO 8601 format. format: date-time links: type: object additionalProperties: type: string description: >- A map of link names to associated URIs, providing additional resources or information related to the batch operation. requestedAt: type: string description: >- The date and time when the batch operation was requested, in ISO 8601 format. format: date-time results: type: array description: >- An array of results from the batch operation, each represented by a JournalFetchResponse object. items: $ref: '#/components/schemas/JournalFetchResponse' startedAt: type: string description: >- The date and time when the batch operation started, in ISO 8601 format. format: date-time status: type: string description: >- The current status of the batch operation. Valid values include 'PENDING', 'PROCESSING', 'CANCELED', and 'COMPLETE'. enum: - CANCELED - COMPLETE - PENDING - PROCESSING BatchResponseJournalFetchResponseWithErrors: required: - completedAt - results - startedAt - status type: object properties: completedAt: type: string description: >- The date and time when the batch operation was completed, in ISO 8601 format. format: date-time errors: type: array description: >- An array of standard errors, detailing any issues encountered during the batch operation. items: $ref: '#/components/schemas/StandardError' links: type: object additionalProperties: type: string description: >- A map of link names to associated URIs, providing additional resources or documentation related to the batch operation. numErrors: type: integer description: The number of errors encountered during the batch operation. format: int32 requestedAt: type: string description: >- The date and time when the batch operation was requested, in ISO 8601 format. format: date-time results: type: array description: >- An array of journal fetch responses, each representing a successful fetch attempt. items: $ref: '#/components/schemas/JournalFetchResponse' startedAt: type: string description: >- The date and time when the batch operation started, in ISO 8601 format. format: date-time status: type: string description: >- The current status of the batch operation. Valid values include 'PENDING', 'PROCESSING', 'CANCELED', and 'COMPLETE'. enum: - CANCELED - COMPLETE - PENDING - PROCESSING JournalFetchResponse: required: - currentOffset - expiresAt - url type: object properties: currentOffset: type: string description: A UUID string indicating the current offset for pagination purposes. format: uuid expiresAt: type: string description: The date and time when the URL will expire, in ISO 8601 format. format: date-time url: type: string description: >- A temporary, pre-signed URL for downloading this entry's JSON file. Request it without an `Authorization` header. StandardError: required: - category - context - errors - links - message - status type: object properties: category: type: string description: A string indicating the category of the error. context: type: object additionalProperties: type: array items: type: string description: >- An object containing additional context about the error condition, with keys as context names and values as arrays of strings. errors: type: array description: >- An array of ErrorDetail objects that provide further information about the error. items: $ref: '#/components/schemas/ErrorDetail' id: type: string description: A string that uniquely identifies this error instance. links: type: object additionalProperties: type: string description: >- An object mapping link names to associated URIs that provide documentation or remediation steps related to the error. message: type: string description: A string containing a human-readable message describing the error. status: type: string description: A string representing the status of the error. subCategory: type: object properties: {} description: An object providing more specific details about the error category. description: Ye olde error Error: required: - category - correlationId - message type: object properties: category: type: string description: The error category. context: type: object additionalProperties: type: array items: type: string description: >- Context about the error condition, represented as an object with additional properties. example: >- {invalidPropertyName=[propertyValue], missingScopes=[scope1, scope2]} correlationId: type: string description: >- A unique identifier for the request. Include this value with any error reports or support tickets. format: uuid example: aeb5f871-7f07-4993-9211-075dc63e7cbf errors: type: array description: >- Further information about the error, represented as an array of ErrorDetail objects. items: $ref: '#/components/schemas/ErrorDetail' links: type: object additionalProperties: type: string description: >- A map of link names to associated URIs containing documentation about the error or recommended remediation steps. message: type: string description: >- A human readable message describing the error along with remediation steps where appropriate. example: An error occurred subCategory: type: string description: >- A specific category that contains more specific detail about the error. description: >- Represents an error response returned by the API when an operation fails. This component is used in various endpoints to provide detailed information about the error encountered. example: message: Invalid input (details will vary based on the error) correlationId: aeb5f871-7f07-4993-9211-075dc63e7cbf category: VALIDATION_ERROR links: knowledge-base: https://www.hubspot.com/products/service/knowledge-base ErrorDetail: required: - message type: object properties: code: type: string description: The status code associated with the error detail. context: type: object additionalProperties: type: array items: type: string description: >- Context about the error condition, represented as an object with additional properties. Each property is an array of strings providing further context. example: '{missingScopes=[scope1, scope2]}' in: type: string description: The name of the field or parameter in which the error was found. message: type: string description: >- A human readable message describing the error along with remediation steps where appropriate. This is a required property. subCategory: type: string description: >- A specific category that contains more specific detail about the error. description: >- Represents detailed information about an error that occurred in the API. This component is used to provide additional context and specifics about errors, typically as part of an error response. responses: Error: description: An error occurred. content: '*/*': schema: $ref: '#/components/schemas/Error' ````