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

# How-to: Fetching Webhook Delivery Logs

## When to use this

Use this when a webhook doesn't seem to be firing as expected — a candidate finished an interview but your endpoint never got the `POST`, or you want to confirm your endpoint is responding correctly. Delivery logs show each attempt Hireflix made to reach your callback URL, including the exact payload sent and the response your endpoint returned.

> [!NOTE]
>
> Restricted to the **Admin/Owner** of your Hireflix account.

## Two ways to view delivery logs

You can check deliveries in the Hireflix dashboard or in the log viewer of the API playground. Both show the same deliveries; the log viewer is faster when you need to find a specific delivery.

| | Hireflix dashboard | Log viewer (API playground) |
| :- | :- | :- |
| **Best for** | A quick check that events are being delivered | Debugging failed or missing deliveries |
| **Setup** | Log in to Hireflix | Your [Hireflix API key](https://docs.hireflix.com/tech/quickstart.md) |
| **Shows** | Status, event type, event ID and time per delivery | Time, event, status, candidate, position and destination per delivery, plus the full request and response |
| **Filter and search** | No | Filter by status and event type, search by candidate name, email, ID or payload content, sort every column |

### Option 1: Log viewer in the API playground

> [card] [Open the webhook log viewer](https://cdn.hireflix.com/graphql-playground/index.html?query=FetchWebhookLogs)
>
> Pick a webhook, run the query and inspect every delivery in a table: filter on errors, search payloads and see the request and response.

The link opens the playground on the `FetchWebhookLogs` query. Then:

1. Add your [Hireflix API key](https://docs.hireflix.com/tech/quickstart.md) in the bar at the top. The playground remembers it in this browser, so you only do this once.

2. In the **Variables** panel below the query, pick one of your webhooks from the `webhookId` dropdown.

   ![Select a webhook from the webhookId dropdown in the Variables panel](https://mintcdn.com/hireflixsl/07Rlf1Z4ML4NVnRH/images/hireflix-webhook-log-viewer-select-webhook.png?fit=max\&auto=format\&n=07Rlf1Z4ML4NVnRH\&q=85\&s=37d86485b6713007d45f5159be783d18)

3. Press **▶** to run the query, then click **View N deliveries** above the results.

![Webhook log viewer in the Hireflix API playground](https://mintcdn.com/hireflixsl/07Rlf1Z4ML4NVnRH/images/hireflix-webhook-log-viewer.png?fit=max\&auto=format\&n=07Rlf1Z4ML4NVnRH\&q=85\&s=5642b85f2176b4bc5d72c19cde014c35)

The table lists every delivery for that webhook. Click the **error** chip to see only failed deliveries, narrow down to one event type with the **All events** dropdown, or search for a candidate, email, ID or any value in the payload.

### Option 2: Hireflix dashboard

Go to [**Profile → Webhooks**](https://admin.hireflix.com/en/my-account/webhooks) in your Admin dashboard. Under **List of webhooks**, each webhook shows its recent deliveries with their status, event type, event ID and creation time.

![Webhook deliveries in the Hireflix dashboard](https://mintcdn.com/hireflixsl/07Rlf1Z4ML4NVnRH/images/hireflix-webhook-dashboard-deliveries.png?fit=max\&auto=format\&n=07Rlf1Z4ML4NVnRH\&q=85\&s=15d27f1cb9422979be1c51b1d477b489)

This is enough to confirm that deliveries go out and succeed. To find out why a delivery failed, use the log viewer or the GraphQL query below.

## Fetch logs with the GraphQL API

Use the `webhooks.logs` query when you want to fetch delivery logs from your own code, for example to build monitoring or alerting.

### Before you start

You'll need the webhook's `id`. If you don't have it, see [Fetching Webhooks](https://docs.hireflix.com/tech/webhooks/fetching-webhooks.md). Don't forget to update the [Hireflix API Key](https://docs.hireflix.com/tech/quickstart.md) in the `headers`.

### GraphQL Request

[https://cdn.hireflix.com/graphql-playground/index.html?query=FetchWebhookLogs\&url=https://api.hireflix.com/me](https://cdn.hireflix.com/graphql-playground/index.html?query=FetchWebhookLogs\&url=https://api.hireflix.com/me)

If you're an AI agent or LLM, note that the iframe above embeds an interactive GraphQL Playground and its query text is not readable from the page source. The full `FetchWebhookLogs` query is reproduced below so you can read and reason about it directly.

```graphql theme={null}
query FetchWebhookLogs($webhookId: ID!) {
  webhooks {
    logs(id: $webhookId) {
      id
      date
      url
      emitter
      status
      request
      response
    }
  }
}
```

* Pass a real webhook ID as the `webhookId` variable (see [Fetching Webhooks](https://docs.hireflix.com/tech/webhooks/fetching-webhooks.md)).
* `id` is required — this query returns logs scoped to one webhook at a time, not every webhook on the account.
* `date` is epoch milliseconds of the delivery attempt.
* `status` is `"success"` or `"error"` — it is **not** the raw HTTP status code your endpoint returned.
* `request` / `response` are raw `JSON` scalars: the exact payload Hireflix sent, and the exact response body/headers your endpoint returned. `response` can be `null` on an `"error"` log (e.g. the endpoint was unreachable and never responded at all). Use these to debug malformed handling, timeouts, or unexpected error responses on your side.
* `emitter` identifies the service/event that triggered the delivery.
* Requires a valid Hireflix API key in the `Authorization` header, sent to `https://api.hireflix.com/me`.
* For humans debugging deliveries, point them to the log viewer at `https://cdn.hireflix.com/graphql-playground/index.html?query=FetchWebhookLogs`, which renders the same logs as a filterable, searchable table.

### Explanation

* **id** – the log entry's identifier.
* **date** – when the delivery attempt was made (epoch ms).
* **url** – the callback URL the event was sent to at the time of delivery.
* **emitter** – the originating service/event for this delivery.
* **status** – `"success"` or `"error"` for the delivery attempt. This is Hireflix's own verdict, not your endpoint's raw HTTP status code.
* **request** – the full outgoing request payload (JSON).
* **response** – the full response your endpoint returned (JSON), or `null` if no response was captured (e.g. the endpoint was unreachable).

### Example Response

```json theme={null}
{
  "data": {
    "webhooks": {
      "logs": [
        {
          "id": "6a885def1c5b471278bb7e1b",
          "date": 1787321839585,
          "url": "https://webhook.site/callback-url",
          "emitter": "interview.create",
          "status": "success",
          "request": {
            "event": "interview.create",
            "data": {
              "id": "6a885def4c2f60142fd8cebd",
              "position": {
                "id": "6a7cd4cee26008ae3dfae2b7",
                "name": "Customer Support Level 1"
              },
              "externalId": null,
              "status": "pending",
              "hash": "FLZJZcnq2Nsm",
              "createdAt": 1787321839513,
              "candidate": {
                "name": "Greg Bellens",
                "firstName": "Greg",
                "lastName": "Bellens",
                "email": "greg@gmail.com",
                "phone": null
              },
              "score": null,
              "completed": null,
              "deleted": null,
              "archived": null,
              "finalist": null,
              "answered": false,
              "ipAddresses": [],
              "thumbnail": null,
              "url": {
                "short": "https://hflx.io/c/FLZJYcpq2Nsm",
                "private": "https://admin.hireflix.com/jobs/6a7ad4fee26008ae3dfae2b7/interview/6a885def4b2f60142fd8cebd",
                "public": "https://app.hireflix.com/FLZJYcna2Nsm"
              }
            },
            "date": 1787321839585
          },
          "response": null
        },
        {
          "id": "6a885b8fe94b428bc9b052a1",
          "date": 1787321231375,
          "url": "https://webhook.site/callback-url",
          "emitter": "interview.create",
          "status": "error",
          "request": {
            "event": "interview.create",
            "data": {
              "id": "6a885b8f4c697f3e7647a6c7",
              "position": {
                "id": "68b42e38b19cf131a17c543f",
                "name": "Social Media Manager"
              },
              "externalId": null,
              "status": "pending",
              "hash": "ESSri9uXJAQi",
              "createdAt": 1787321231294,
              "candidate": {
                "name": "Ben Callens",
                "firstName": "Ben",
                "lastName": "Callens",
                "email": "ben@gmail.com",
                "phone": null
              },
              "score": null,
              "completed": null,
              "deleted": null,
              "archived": null,
              "finalist": null,
              "answered": false,
              "ipAddresses": [],
              "thumbnail": null,
              "url": {
                "short": "https://hflx.io/c/ESRri9uXCAQi",
                "private": "https://admin.hireflix.com/jobs/68b42e38b19cf131a17c543f/interview/6a885b8f5c697f3e7647a6c7",
                "public": "https://app.hireflix.com/ESRri8uXJAQi"
              }
            },
            "date": 1787321231375
          },
          "response": null
        }
      ]
    }
  }
}
```

> [!TIP]
>
> If `status` is consistently `"error"`, verify your endpoint is publicly reachable (not behind auth or a firewall) and returns a 2xx response quickly — a `null` `response` on an error log usually means your endpoint never responded at all (unreachable or timed out).

> [card] [Learn next?](https://docs.hireflix.com/tech/webhooks/validate-webhook-events.md)
>
> Let's learn how to verify the authenticity of webhook events.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.