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

# List journal sync jobs

> Lists general-ledger sync runs, newest first, with their status and counts.

By default, only completed runs are returned. Set `include_all=true` to add failed, canceled and `hanged` runs, or `include_in_progress=true` to add runs that have not finished.

`status_counts` counts all statuses, not only the completed runs of the default. A failed count can be above zero when the page shows only completed runs.


## OpenAPI

````yaml openapi-public-preview.json GET /v1/journal-entries/syncs
openapi: 3.1.0
info:
  title: Entendre API
  version: 1.0.0
  description: Programmatic access to crypto-native accounting and treasury operations.
servers:
  - url: https://api.entendre.finance
    description: Production API.
security:
  - ApiKey: []
tags:
  - name: Organization
    description: Read your organization profile and find members for agent assignments.
  - name: Transactions
    description: Find transactions, inspect their details and create manual records.
  - name: Sources
    description: >-
      Manage wallets, exchange accounts, bank accounts and other transaction
      sources.
  - name: Assets
    description: Inspect asset acquisitions, remaining quantities and cost basis.
  - name: Journals
    description: >-
      Create and post journal entries, correct eligible entries and sync posted
      journals to a connected general ledger.
  - name: Documents
    description: >-
      Upload documents, check processing status and link supporting evidence to
      transactions.
  - name: Legal Entities
    description: Manage the legal entities used in your accounting records.
  - name: Ledger Accounts
    description: Manage your chart of accounts and find accounts for journal entries.
  - name: Tags
    description: Create and manage tags to classify your records.
  - name: Accruals
    description: >-
      Create and post accruals, inspect their status and reverse eligible
      entries.
  - name: Cash Application
    description: Match deposits to invoices and manage the resulting cash applications.
  - name: Classification
    description: >-
      Classify transactions in a batch, post eligible entries and inspect the
      results.
  - name: Revaluation
    description: Run asset revaluations for an accounting period and check their results.
  - name: Accounting Periods
    description: Check whether a period is ready to close, then close or reopen it.
  - name: Income Statement
    description: View revenue, expenses and net income for a reporting period.
  - name: Balance Sheet
    description: View assets, liabilities and equity as of a reporting date.
  - name: Trial Balance
    description: Review ledger account balances and debit and credit totals.
  - name: Closing Positions
    description: View asset positions at the end of a reporting period.
  - name: Treasury Balances
    description: Review treasury balances by asset and source.
  - name: Realized Gains & Losses
    description: Review realized gains and losses from asset dispositions.
  - name: Asset Tax Lots
    description: Inspect asset tax lots, remaining quantities and cost basis.
  - name: Schedule of Dispositions
    description: >-
      Review asset dispositions and their proceeds, cost basis and gains or
      losses.
  - name: Financial Insights
    description: Review financial insights for your selected reporting context.
  - name: Agents
    description: Create agents, schedule their work and inspect their runs.
  - name: Memory
    description: Read, search and maintain the memory files your agents use.
  - name: Connections
    description: Connect providers, manage authorization and disconnect.
  - name: GL Mapping
    description: >-
      Map ledger accounts and legal entities to your ERP. Import legal entities,
      tags and chart of accounts.
  - name: Request
    description: Request information, documents or connections from a client.
  - name: Client
    description: Manage your firm’s client relationships.
  - name: Team
    description: Invite team members and manage their access to your firm.
  - name: Settings
    description: Read and update your firm settings.
paths:
  /v1/journal-entries/syncs:
    get:
      tags:
        - Journals
      summary: List journal sync jobs
      description: >-
        Lists general-ledger sync runs for the organization, newest first. One
        row per run: an accounting period pushed to one provider, with its
        synced and failed counts. Only completed runs are returned by default;
        include_all adds failed, canceled and hanged runs, include_in_progress
        adds running ones. Always read status_counts before reporting sync
        health, because it tallies the runs the default hides.
      operationId: list_journal_sync_jobs
      parameters:
        - name: integration_type
          in: query
          required: false
          description: Restrict to one destination provider.
          schema:
            type: string
            enum:
              - quickbooks
              - xero
              - netsuite
              - dualentry
              - campfire
        - name: include_all
          in: query
          required: false
          description: Include failed, canceled and hanged runs alongside completed ones.
          schema:
            type: boolean
            default: false
        - name: include_in_progress
          in: query
          required: false
          description: Include runs that have started but not finished.
          schema:
            type: boolean
            default: false
        - name: limit
          in: query
          required: false
          description: Maximum number of records to return.
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 50
        - name: cursor
          in: query
          required: false
          description: >-
            The `next_cursor` value from the previous page. Keep the other
            filters unchanged.
          schema:
            type: string
      responses:
        '200':
          description: >-
            Sync runs in the authenticated organization. An empty data array
            means no run matches; status_counts still reports what the filters
            hid.
          headers:
            X-Request-Id:
              description: Support correlation ID.
              schema:
                type: string
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/JournalSync'
                    description: The records.
                  has_more:
                    type: boolean
                    description: Whether another page is available.
                  next_cursor:
                    type:
                      - string
                      - 'null'
                    description: Cursor for the next page, or `null` on the last page.
                  status_counts:
                    type: object
                    additionalProperties:
                      type: integer
                    description: Run counts by status. Statuses with no runs are omitted.
                required:
                  - data
                  - has_more
                  - next_cursor
                  - status_counts
                additionalProperties: false
              example:
                data:
                  - id: sh_507f1f77bcf86cd799439011
                    organization_id: org_507f1f77bcf86cd799439011
                    accounting_period_id: ap_507f1f77bcf86cd799439011
                    created_by: usr_507f1f77bcf86cd799439011
                    integration_type: quickbooks
                    job_status: completed
                    synced_count: 12
                    failed_count: 0
                    total_count: 12
                    completed_at: '2026-08-31T12:01:00Z'
                    error_message: null
                    created_at: '2026-08-31T12:00:00Z'
                    updated_at: '2026-08-31T12:01:00Z'
                has_more: false
                next_cursor: null
                status_counts:
                  COMPLETED: 1
        '400':
          description: >-
            The request is invalid. `error.fields` lists the fields to correct.
            Nothing was changed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: VALIDATION_ERROR
                  message: Invalid path, query or request body.
                  request_id: req_example
        '401':
          description: The API key is missing, invalid or expired.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: UNAUTHORIZED
                  message: Authentication is required.
                  request_id: req_example
        '403':
          description: >-
            The API key does not have the required scope or is not associated
            with a user, or the action needs a review in the dashboard.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: FORBIDDEN
                  message: Insufficient access to organization
                  request_id: req_example
        '404':
          description: The resource does not exist, or your organization cannot access it.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: RESOURCE_NOT_FOUND
                  message: Resource not found
                  request_id: req_example
        '429':
          description: >-
            Too many requests. If the response has a `Retry-After` header, wait
            that many seconds before you retry. Otherwise, read `error.message`.
          headers:
            Retry-After:
              description: Seconds to wait before retrying.
              schema:
                type: integer
                minimum: 1
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: RATE_LIMITED
                  message: Rate limit exceeded. Retry after 30s.
                  request_id: req_example
        '500':
          description: >-
            An unexpected error occurred. A write can still have taken effect;
            check the resource before you retry. Give the `request_id` to
            support.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: INTERNAL_ERROR
                  message: Internal server error
                  request_id: req_example
        '503':
          description: >-
            A service that this operation needs is unavailable. If the response
            has a `Retry-After` header, wait that many seconds. Check for
            earlier accepted work before you send the request again.
          headers:
            Retry-After:
              description: Seconds to wait before retrying.
              schema:
                type: integer
                minimum: 1
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: SERVICE_UNAVAILABLE
                  message: Service unavailable.
                  request_id: req_example
components:
  schemas:
    JournalSync:
      type: object
      description: >-
        One general-ledger sync run: an accounting period's worth of journals
        pushed to one provider. A single Sync journals request can produce
        several runs.
      properties:
        id:
          type: string
          description: Sync run ID.
          example: sh_507f1f77bcf86cd799439011
        organization_id:
          type:
            - string
            - 'null'
          description: Owning organization.
        accounting_period_id:
          type:
            - string
            - 'null'
          description: Accounting period the run covered.
        created_by:
          type:
            - string
            - 'null'
          description: User who started the run. Null when system-initiated.
        integration_type:
          type: string
          description: Destination general-ledger provider.
          enum:
            - quickbooks
            - xero
            - netsuite
            - dualentry
            - campfire
        job_status:
          type:
            - string
            - 'null'
          description: >-
            Run status. `null` for older runs whose status cannot be read; count
            them as unknown, not as successes.
          enum:
            - started
            - in_progress
            - completed
            - job_failed
            - canceled
            - hanged
            - null
        synced_count:
          type:
            - integer
            - 'null'
          description: Journals the provider accepted.
        failed_count:
          type:
            - integer
            - 'null'
          description: Journals the provider rejected.
        total_count:
          type:
            - integer
            - 'null'
          description: Journals selected for the run.
        completed_at:
          type:
            - string
            - 'null'
          format: date-time
          description: Time the job finished (ISO 8601).
        error_message:
          type:
            - string
            - 'null'
          description: Failure reason when the whole run failed.
        created_at:
          type:
            - string
            - 'null'
          format: date-time
          description: ISO 8601 UTC timestamp.
        updated_at:
          type:
            - string
            - 'null'
          format: date-time
          description: ISO 8601 UTC timestamp.
      required:
        - id
        - organization_id
        - accounting_period_id
        - created_by
        - integration_type
        - job_status
        - synced_count
        - failed_count
        - total_count
        - completed_at
        - error_message
        - created_at
        - updated_at
      additionalProperties: false
    ErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
            - request_id
          properties:
            code:
              type: string
              description: Machine-readable error code.
            message:
              type: string
              description: Technical description for developers.
            fields:
              type: object
              additionalProperties:
                type: string
              description: >-
                Present only on VALIDATION_ERROR. Maps failing field paths to
                reason strings.
            details:
              type: object
              additionalProperties: true
              description: >-
                Optional redacted diagnostic details. Request validation uses
                fields or field_errors.
            suggested_action:
              type: string
              description: A suggested next step.
            documentation_url:
              type: string
              format: uri
              description: Link to documentation about this error.
            request_id:
              type: string
              description: Unique request ID for support escalation.
          description: Error details.
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: X-API-Key
      description: >-
        Your organization API key. Some operations also need a key that is
        associated with a user; their pages say so.

````