Ackogeneralinsurance Webhooks

generated: '2026-09-06'
method: searched
source: https://www.acko.com/enterprise/documentation/enterprise.html
asyncapi_published: false
note: >-
  ACKO publishes no AsyncAPI document and no webhook reference page. The three callback surfaces
  below are stated by ACKO in its own API documentation (the tag descriptions rendered on the
  enterprise docs page and carried in the published OpenAPI), but no subscription endpoint, event
  name, payload schema, retry policy or signature scheme is published for any of them. Recorded as an
  advertised-but-unspecified webhook surface — nothing here is invented, and nothing here is callable
  from the published contract alone.
webhooks:
- name: policy-issuance-payment-status-callback
  area: Policy Issuance
  statement_verbatim: >-
    "This section details the mandatory request headers, idempotency keys for preventing duplicate
    transactions, payment status callbacks, and performance benchmarks for both synchronous and
    asynchronous integration modes."
  payload_schema: undocumented
  subscription: undocumented
- name: claim-status-updates
  area: Claims Management
  statement_verbatim: >-
    "This section guides partners through creating First Notice of Loss (FNOL), uploading supporting
    documentation, and monitoring claim status through automated webhooks. Our claims infrastructure
    is designed to provide real-time status updates..."
  payload_schema: undocumented
  subscription: undocumented
  related_operations: [createClaim, getClaim]
- name: gig-task-start-stop
  area: GIG
  statement_verbatim: >-
    "The API includes webhooks for task start/stop events to ensure precise coverage periods for gig
    economy platforms."
  payload_schema: undocumented
  subscription: undocumented
  related_operations: [gigIssuanceV1, gigIssuanceV2, endorsePolicyGIGSessionCreationV1, endorsePolicyGIGSessionCreationV2]
gaps:
- No AsyncAPI or event catalog is published; an AsyncAPI 3.0 document would make these three surfaces callable.
- No webhook signing / verification scheme is documented.
- No delivery-retry or replay policy is documented.