check_in_reporting

A check-in missed its schedule, or started reporting again.

Fields

The table lists every field of the body. You can validate a delivery against this event’s JSON Schema.

Field	Type	Description
`event` required	"check_in_reporting"
`message` required	string	A one-line summary of the event, as notifications show it.
`payload_version` required	string	The integration's payload version. Allowed value: `v3`.
`actor`	object	The person who caused the event. Absent when Honeybadger did.
`actor.id` required	string \| null	The user's ID, or null when the person has no Honeybadger account.
`actor.name` required	string \| null
`actor.email` required	string \| null
`credential`	object	The API token or OAuth grant the event was caused through. Absent when the event wasn't caused through the API.
`credential.type` required	string	`ApiToken` for an API token, `OauthAccessToken` for an OAuth grant.
`credential.id` required	string
`credential.name` required	string \| null	The token's name. For an OAuth grant, the name the user gave the connection, or the application's name if none.
`project` required	object	The project the event belongs to.
`project.id` required	string
`project.name` required	string
`project.language` required	string \| null
`project.created_at` required	date-time
`project.links` required	object	Links into the Honeybadger web UI.
`project.links.web` required	uri	The resource's page in the Honeybadger web UI, as an absolute URL. Resources without a page, such as outages and deploys, don't have `links`. For a project provisioned through Heroku, error, notice and comment links go through Heroku's single sign-on.
`links` required	object	The page to open for this event.
`links.web` required	uri	The resource's page in the Honeybadger web UI, as an absolute URL. Resources without a page, such as outages and deploys, don't have `links`. For a project provisioned through Heroku, error, notice and comment links go through Heroku's single sign-on.
`check_in` required	object	The check-in the event is about.
`check_in.id` required	string
`check_in.project_id` required	string
`check_in.name` required	string \| null
`check_in.slug` required	string \| null
`check_in.schedule_type` required	string	`simple` expects a report every `report_period`. `cron` expects reports on a cron schedule and requires `cron_schedule`. Allowed values: `simple`, `cron`. Default: `"simple"`.
`check_in.state` required	string	Allowed values: `pending`, `reporting`, `missing`, `paused`.
`check_in.reported_at` required	date-time \| null
`check_in.expected_at` required	date-time \| null
`check_in.missed_count` required	integer
`check_in.created_at` required	date-time
`check_in.links` required	object	Links into the Honeybadger web UI.
`check_in.links.web` required	uri	The resource's page in the Honeybadger web UI, as an absolute URL. Resources without a page, such as outages and deploys, don't have `links`. For a project provisioned through Heroku, error, notice and comment links go through Heroku's single sign-on.

Example

{
  "event": "check_in_reporting",
  "message": "[Billing API] REPORTING: Nightly invoice run is reporting again",
  "project": {
    "id": "H99upHsM",
    "name": "Billing API",
    "language": "ruby",
    "created_at": "2026-10-21T12:36:26Z",
    "links": {
      "web": "https://app.honeybadger.io/projects/H99upHsM/faults"
    }
  },
  "check_in": {
    "id": "b3IAob",
    "project_id": "H99upHsM",
    "name": "Nightly invoice run",
    "slug": "nightly-invoice-run",
    "schedule_type": "simple",
    "state": "reporting",
    "reported_at": "2026-10-21T12:36:26Z",
    "expected_at": "2026-10-22T12:36:26Z",
    "missed_count": 0,
    "created_at": "2026-08-22T12:36:26Z",
    "links": {
      "web": "https://app.honeybadger.io/projects/H99upHsM/check_ins/b3IAob"
    }
  },
  "links": {
    "web": "https://app.honeybadger.io/projects/H99upHsM/check_ins/b3IAob"
  },
  "payload_version": "v3"
}