# List an integration's error log

```http
GET https://secure.yoprint.com/v1/api/store/{team_slug}/setting/external_integration/{id}/logs
```

- API version: v1
- Operation ID: `v1_public_external_integration_logs`
- Section: Team settings › [Integrations](https://developer.yoprint.com/reference/integrations.md)
- Web page: https://developer.yoprint.com/reference/integrations/v1-external-integration-logs/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Returns the sync errors an integration recorded, newest first, a page at a time (the team's page size). Only QuickBooks Online keeps a log here (`has_logs: true`); for every other integration the answer is `data: null`.

Each entry has `type`, `error_code`, `error_message`, `error_payload`, `retryable` and `created_at`, and names the order it is about in `order` (or null). A QuickBooks payment that is held gets one entry per hold, with the QuickBooks Payment in `quickbooks_payment_id` and QuickBooks' own words in `quickbooks_message`. Provider answers are logged with secrets removed. The `{id}` is the integration's id from the list.

## Permission

Any member of the team, whatever their role. This is wider than the web app, whose Settings pages need Manage Settings: on the API only changes need it. AI apps (MCP connections) need Manage Settings to read it.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.
- `id` (string, required): The integration, from the integration list. Its hash id from an earlier answer; there is no unique key for it. Example `d9ZxWgBz09mDFq`.

## Request body

This operation takes no request body.

### Example request

```bash
curl 'https://secure.yoprint.com/v1/api/store/your-team/setting/external_integration/d9ZxWgBz09mDFq/logs' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1'
```

## Response

`200` Successful response.

Fields:

- `data` (array of objects, required)
  - Each item:
    - `created_at` (string (date-time), optional)
    - `error_code` (string | null, optional)
    - `error_message` (string | null, optional)
    - `error_payload` (object | array | string | null, optional): What the provider sent back, when it did: for a QuickBooks refusal, QuickBooks' detail text.
    - `helpscout_article_id` (string | null, optional)
    - `id` (string, optional)
    - `order` (object | null, optional): The sales order or quote the entry is about, or null.
      - `deleted` (boolean, required)
      - `id` (string, required): The order's id, as the order operations take it.
      - `scoped_id` (string, required): The number people see, such as `SO1001`. Not an id.
      - `type` (string, required): One of: `"sales_order"`, `"quote"`.
    - `quickbooks_message` (string | null, optional): What QuickBooks said, when it refused a payment.
    - `quickbooks_payment_id` (string | null, optional): The QuickBooks Payment the entry is about, when it is about one.
    - `retryable` (boolean, optional)
    - `type` (string, optional)
- `status` (integer, required)
- `success` (boolean, required)
- `pagination` (object, optional)
  - `count` (integer, required)
  - `currentPage` (integer, required)
  - `links` (object | array of any, required): Links to the neighbouring pages: `previous` and `next`, each present only when that page exists. An empty list, `[]`, when there is only one page.
    - `next` (string (uri), optional): The next page.
    - `previous` (string (uri), optional): The previous page.
  - `perPage` (integer, required)
  - `total` (integer, required)
  - `totalPages` (integer, required)

Example response:

```json
{
  "data": [
    {
      "created_at": "2026-10-30T09:00:00+00:00",
      "error_code": "6000",
      "error_message": "(Invoice) A business validation error has occurred while processing your request",
      "error_payload": "Business Validation Error: The customer is inactive.",
      "helpscout_article_id": null,
      "id": "i91i7ESuTjjC9i",
      "order": {
        "deleted": false,
        "id": "V4keXwwxMQyXw7",
        "scoped_id": "SO1001",
        "type": "sales_order"
      },
      "quickbooks_message": null,
      "quickbooks_payment_id": null,
      "retryable": false,
      "type": "qbo_sync_endpoint_error"
    }
  ],
  "pagination": {
    "count": 1,
    "currentPage": 1,
    "links": [],
    "perPage": 50,
    "total": 1,
    "totalPages": 1
  },
  "status": 200,
  "success": true
}
```

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
- `403` You are not allowed to do this. `api_access_not_in_plan`: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only `{"message": "Insufficient Permission"}`. Other refusals use the error envelope, with `unauthorized` or `user_is_not_authorized`.
- `404` Not found. `page_not_found`: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. `code: null`, with a message that starts "No query results for": there is no record with that id.
  - When: No integration of your team has this id. `error.code` is null; `error.message` names the record type. Fix: Use an id from the list.
- `422` The request was refused and changed nothing. `validation_failed` lists what to fix in `error.fields`; other codes name a business rule, explained in `error.message`. A few checks answer with only `{"message": "..."}`. An operation that calls another service (a payment provider, a carrier, an accounting app) can answer `connect_timeout` ("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.
  - When: Shopify is not in your plan (`plan_limitation`). Fix: Upgrade the plan.

## Related

- [Get an integration](https://developer.yoprint.com/reference/integrations/v1-external-integration-show.md): `GET /v1/api/store/{team_slug}/setting/external_integration/{external_integration_reference}`