Harri · AsyncAPI Specification

Harri Webhooks

Version

View Spec View on GitHub Human ResourcesWorkforce ManagementHospitalityRestaurantSchedulingTime and AttendancePayrollTalent AcquisitionLabor ComplianceHCMAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-08-04'
method: searched
source: https://developer.harri.com/webhook-event-notifications/ (member-gated) plus the Event and Subscriptions
  operations in openapi/harri-employee-openapi.yml
spec_type: Webhooks
asyncapi:
  published: false
  note: No AsyncAPI document is published anywhere on the Harri surface. Probed /asyncapi.yaml, the developer
    portal and the HarriLLC GitHub org on 2026-08-04.
event_surface:
  exists: true
  documentation:
    url: https://developer.harri.com/webhook-event-notifications/
    title: Webhook Event Notifications
    http_status: 200
    access: member-gated
    published: '2025-06-25'
    note: The page is publicly reachable and publicly titled, but its body requires a developer-portal
      account, so the event-type catalog could not be captured without credentials.
  delivery: webhook event notifications (per the documentation title) with a queryable event log via the
    REST API
rest_event_operations:
- operationId: v2_events_list
  method: GET
  path: /api/v2/events
  description: Retrieve a list of events, filterable by event_code, location_id, status and a published_gte/published_lte
    window
  parameters:
  - event_code
  - location_id
  - status
  - published_gte
  - published_lte
  - limit
  - page
- operationId: GetEventById
  method: GET
  path: /api/v1/events/{eventId}
  description: Retrieve a single event
- operationId: ListFranchiseeEvents
  method: GET
  path: /api/v1/franchisees/{franchiseeId}/events
  description: List events for a franchisee
  parameters:
  - status
  - event_code
  - published_gte
  - published_lte
- operationId: franchisees_v2_events_list
  method: GET
  path: /api/v2/franchisees/{franchiseeId}/events
  description: List franchisee events (v2)
- operationId: FranchiseesGetEventById
  method: GET
  path: /api/v1/franchisees/{franchiseeId}/events/{eventId}
  description: Retrieve a single franchisee event
- operationId: GetEvents
  method: GET
  path: /api/v1/events
  description: Retrieve events (deprecated)
  deprecated: true
subscription_operations:
- operationId: ListClientSubscriptions
  method: GET
  path: /api/v1/subscriptions
  description: Retrieve all subscriptions for the authenticated client
- operationId: ListFranchiseeSubscriptions
  method: GET
  path: /api/v1/franchisees/{franchiseeId}/subscriptions
  description: Retrieve all subscriptions for a specific franchisee
event_delivery_status_values:
- SUCCESS
- FAILED
- IN_PROGRESS
event_types: []
note: 'The event-type catalog (the values event_code takes) is not published publicly — the spec types
  event_code as a free-form string and the Webhook Event Notifications doc is member-gated. Recorded as
  an empty event_types[] rather than guessed. Subscriptions are read-only over the API: there are no create,
  update or delete subscription operations in the published spec, so webhook endpoints are provisioned
  out of band.'

Work with this as data

Every AsyncAPI spec here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for asyncapi

4 MCP tools reach this
  • find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/harri-webhooks"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.