> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List journal entries with line + dimension expansion

> Returns journal entries hydrated with their line items and
dimension labels (department / class / project). Sister endpoint
to `GET /v1/journal-entries` (which returns headers only); this
path is the explicit expand contract for read-heavy integrations.
Requires the `accounting:read` scope.




## OpenAPI

````yaml /openapi.yaml get /journal-entries/expand
openapi: 3.1.0
info:
  title: Arcus ERP Public API
  version: 1.0.0
  description: >
    Arcus ERP public REST API. Designed for external integrations and data
    migration.


    **Authentication.** Bearer token (API key) via the `Authorization` header.

    Format: `Authorization: Bearer ark_live_ent_<code>_<random>` (or
    `ark_test_*` for sandbox).

    API keys are issued per-entity in **Settings > Developers > API Keys**.


    **Entity scoping.** The entity is encoded in the API key prefix; routes are
    flat

    (e.g. `/v1/accounts`, `/v1/orders`, `/v1/products`). A small set of platform
    endpoints

    (migration, reconciliation, events, webhook endpoints, API keys) use the

    `/v1/entities/{entity_id}/...` form -- those are noted in their tags.


    **Key capabilities.**
      - Related-resource hydration via `?expand[]=` (see `x-arcus-expand` on each resource).
      - Cursor-based pagination (`starting_after` / `ending_before` / `limit`).
      - Idempotency via the `Idempotency-Key` header.
      - Webhook events for asynchronous notification.
      - Conditional requests / ETag for cache validation.
servers:
  - url: https://api.arcuserp.com/v1
    description: Arcus ERP API (accepts both live `ark_live_*` and test `ark_test_*` keys)
  - url: https://dev-api.arcuserp.com/v1
    description: >-
      Dev sandbox API (test-only data, accepts `ark_test_*` keys against dev
      RDS)
security: []
paths:
  /journal-entries/expand:
    get:
      tags:
        - Accounting
      summary: List journal entries with line + dimension expansion
      description: |
        Returns journal entries hydrated with their line items and
        dimension labels (department / class / project). Sister endpoint
        to `GET /v1/journal-entries` (which returns headers only); this
        path is the explicit expand contract for read-heavy integrations.
        Requires the `accounting:read` scope.
      operationId: listJournalEntriesExpandV1
      parameters:
        - name: status
          in: query
          schema:
            type: string
        - name: from_date
          in: query
          schema:
            type: string
            format: date
        - name: to_date
          in: query
          schema:
            type: string
            format: date
        - $ref: '#/components/parameters/Limit'
      responses:
        '200':
          description: Paginated list of expanded journal entries
          content:
            application/json:
              schema:
                type: object
                properties:
                  object:
                    type: string
                    example: list
                  data:
                    type: array
                    items:
                      type: object
                  has_more:
                    type: boolean
      security:
        - ApiKeyAuth:
            - accounting:read
components:
  parameters:
    Limit:
      name: limit
      in: query
      required: false
      description: |
        Maximum number of records to return per page. Default 25, max 500.
        Use together with starting_after for cursor pagination. For larger
        bulk extraction workflows prefer the migration endpoints.
      schema:
        type: integer
        minimum: 1
        maximum: 500
        default: 25
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      description: |
        API key issued per entity via Settings > Developers > API Keys.
        Each key carries scopes (e.g. orders:read, products:write).
        Bearer token format: Authorization: Bearer ark_live_ent_<code>_<random>
        Test keys use ark_test_ent_<code>_<random>. Both are issued per entity
        via Settings > Developers > API Keys.

````