---
title: "IVR response event"
method: POST
path: "ivr_response_code"
tags: ["webhook"]
---

# IVR response event

`POST ivr_response_code` (webhook)

This event is triggered when a customer answers a response code from an IVR scenario: 
1. Ringover sends you information about an event.
2. You send an HTTP code according to this information (for instance, 200 if it is a successful operation).
3. An IVR with an "Ask for a code" scenario can be created with various HTTP codes and according to the code you return, an event is triggered (recording, redirection, etc.).

> Warning: Announcements must be set in the IVR in order for this webhook to be operational.

> Note: unlike the call events and the Smart Routing webhook, this event is **not signed** — it is sent without an `x-ringover-webhook-signature` (or any signature) header. Do not rely on a signature to authenticate it; if you need to verify the origin, restrict your endpoint to Ringover by other means (e.g. a secret/unguessable URL path or an IP allowlist). Signing this webhook is a known feature request.

## Payload

- WebhookRequestIvrResponseCode
  - `event` string
  - `resource` string
  - `timestamp` number
  - `data` object
    - `code` integer
    - `from_number` string
    - `to_number` string
    - `direction` 'inbound' | 'outbound'
    - `call_id` integer

## Acknowledgement `200`

Successful operation

## Other responses

- `default` — Other response code are ignored

---

[API](https://skmtc.net/ringover/apis/ringover-public-api.md) · [All operations](https://skmtc.net/ringover/apis/ringover-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ringover/ringover-public-api/revisions/9da73dd2f99e/schema)