> ## 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.

# Get the next local journal entry

> Retrieve the entry that follows the given offset. Fails with a `404` if the offset has expired or doesn't exist.

> [accordion] Supported products


## OpenAPI

````yaml specs/2027-03-beta/webhooks-journal-webhooks-journal-v2027-03-beta.json GET /webhooks-journal/journal-local/2027-03-beta/offset/{offset}/next
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-local/2027-03-beta/offset/{offset}/next:
    get:
      tags:
        - Basic
      summary: Retrieve Next Batch
      description: >-
        Retrieve the entry that follows the given offset. Fails with a `404` if
        the offset has expired or doesn't exist.
      operationId: >-
        get-/webhooks-journal/journal-local/2027-03-beta/offset/{offset}/next_/webhooks-journal/journal-local/2027-03-beta/offset/{offset}/next
      parameters:
        - name: offset
          in: path
          description: >-
            The `currentOffset` of the last entry you processed. The entry after
            this offset is returned.
          required: true
          style: simple
          explode: false
          schema:
            type: string
        - name: installPortalId
          in: query
          description: >-
            The ID of the portal installation to filter the webhook journal
            entries. This is an integer value.
          required: false
          style: form
          explode: true
          schema:
            type: integer
            format: int32
      responses:
        '200':
          description: successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/JournalFetchResponse'
        '204':
          description: No journal entry exists after the given offset
          content: {}
        default:
          $ref: '#/components/responses/Error'
          description: ''
      security: []
components:
  schemas:
    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.
    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'

````