> ## 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 journal status

> Retrieve the status of a snapshot request. Use the ID returned when the snapshot was requested: `snapshotStatusId` for CRM object snapshots, or `id` for bulk snapshots.

> [accordion] Supported products


## OpenAPI

````yaml specs/2027-03-beta/webhooks-journal-webhooks-journal-v2027-03-beta.json GET /webhooks-journal/journal/2027-03-beta/status/{statusId}
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/status/{statusId}:
    get:
      tags:
        - Basic
      summary: Retrieve status
      description: >-
        Retrieve the status of a snapshot request. Use the ID returned when the
        snapshot was requested: `snapshotStatusId` for CRM object snapshots, or
        `id` for bulk snapshots.
      operationId: >-
        get-/webhooks-journal/journal/2027-03-beta/status/{statusId}_/webhooks-journal/journal/2027-03-beta/status/{statusId}
      parameters:
        - name: statusId
          in: path
          description: >-
            The ID returned when the snapshot was requested (`snapshotStatusId`
            or the bulk snapshot `id`).
          required: true
          style: simple
          explode: false
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SnapshotStatusResponse'
        default:
          $ref: '#/components/responses/Error'
          description: ''
      security: []
components:
  schemas:
    SnapshotStatusResponse:
      required:
        - id
        - initiatedAt
        - status
      type: object
      properties:
        completedAt:
          type: integer
          description: >-
            When the snapshot finished, in milliseconds since the Unix epoch.
            Absent until the snapshot finishes.
          format: int64
        errorCode:
          type: string
          description: >-
            An optional code indicating the error that occurred, if any.
            Possible values are 'TIMEOUT', 'VALIDATION_ERROR', 'INTERNAL_ERROR',
            and 'PERMISSION_DENIED'.
          enum:
            - INTERNAL_ERROR
            - PERMISSION_DENIED
            - TIMEOUT
            - VALIDATION_ERROR
        id:
          type: string
          description: A unique identifier for the snapshot, represented as a UUID.
          format: uuid
        initiatedAt:
          type: integer
          description: >-
            When the snapshot was requested, in milliseconds since the Unix
            epoch.
          format: int64
        message:
          type: string
          description: >-
            A descriptive message providing additional information about the
            snapshot status or error.
        status:
          type: string
          description: >-
            The current status of the snapshot: `PENDING`, `IN_PROGRESS`,
            `SUCCESS`, `FAILED`, or `EXPIRED`.
          enum:
            - EXPIRED
            - FAILED
            - IN_PROGRESS
            - PENDING
            - SUCCESS
    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'

````