Acall Webhooks

generated: '2026-09-06'
method: searched
source: https://www.acall.jp/help/webhook
docs: https://help.workstyleos.com/hc/ja/webhook
spec_type: none
asyncapi_published: false
summary: >-
  Acall ships a real outbound webhook surface, configured per tenant in the Acall Portal, but publishes no
  AsyncAPI document and no machine-readable event schema. The catalogue below is the webhook contract as the
  provider documents it in its own help centre.
access_note: >-
  The help-centre article is public but both www.acall.jp/help/webhook (301 to help.workstyleos.com) and
  help.workstyleos.com return HTTP 403 with a Cloudflare interstitial to a non-browser client, so the
  content here was read from the publicly indexed copy of that provider page rather than from a direct
  fetch. The page itself is not gated — only our crawler was turned away.
configuration:
  location: Acall Portal (tenant administration)
  fields:
  - name: Webhook名
    name_en: Webhook name
    required: true
  - name: URL
    name_en: Destination URL called when the webhook fires
    required: true
  - name: 署名検証トークン
    name_en: Signature verification token
    required: false
    note: >-
      Generated by Acall on demand via a 生成 (Generate) button, producing a random token. The signing
      algorithm, the header the signature is delivered on, and the canonicalization are NOT documented.
  - name: トリガー設定
    name_en: Trigger selection
    required: true
  - name: 有効
    name_en: Enabled
    required: true
  test_send:
    supported: true
    note: >-
      A トリガー can be selected from a dropdown and 「テスト送信」 (test send) fires a sample request; the
      request and response contents are displayed in the UI. This is the only sandbox-shaped facility Acall
      publishes.
events:
  entity: appointment / internal meeting (アポイント・社内会議)
  triggers:
  - id: appointment.created
    label: アポイント/社内会議の作成
    label_en: Appointment or internal meeting created
  - id: appointment.updated
    label: アポイント/社内会議の更新
    label_en: Appointment or internal meeting updated
  - id: appointment.deleted
    label: アポイント/社内会議の削除
    label_en: Appointment or internal meeting deleted
  note: >-
    Trigger ids above are our normalized labels for the three documented events; Acall does not publish
    machine-readable event-type strings.
fires_on:
- the Acall Portal management screen
- an integrated external calendar
- the Acall mobile app
does_not_fire_on:
- appointments created by the repeat-booking (繰り返し予約) feature
- appointments created by CSV upload
- anything created in Acall Meeting
exclusion_note: >-
  Documented exclusions. These are load-bearing for an integrator: a consumer that treats the webhook as a
  complete change feed for meetings will silently miss three creation paths.
payload:
  schema_published: false
  content_type: unknown
  note: >-
    No payload schema, field list, or example body is published. An integrator learns the shape only from a
    テスト送信 against their own endpoint.
delivery:
  retries: undocumented
  ordering: undocumented
  timeout: undocumented
related_surface:
  note: >-
    The Public API's Event resource (getEvents / getEvent) reads the same entity these webhooks fire on, so
    the webhook is usable as a change signal to be reconciled against the REST read surface.
  cross_reference: openapi/acall-public-api-openapi.yml