---
title: "Answer Call"
method: PATCH
path: "/domains/{domain}/users/{user}/calls/{call_id}/answer"
tags: ["Calls (live/active calls)"]
---

# Answer Call

`PATCH /domains/{domain}/users/{user}/calls/{call_id}/answer`

## Path parameters

- `domain` string, required — This is the main organization name. This is used to link resource to its group/tenant/organization/enterprise. Then using in path for GET you can set to "~" to use the domain name linked to your token/key instead of the domain name itself when reading for your own domain.
- `user` string, required — This is the main user extension for the user account. ~ can be used to mean "my account" which will extract the user from the token/key used for authentication.
- `call_id` string, required

## Request body

- CallActions
  - `call-term-user` string — This is the new forward location for the call to be transfered to. Do NOT set when using for attended transfer process.
  - `hostname` string, hostname — Required only for supervised/assisted transfers, this is the hostname where the call currently resides.
  - `call-destination-session-id` string — Required only for supervised/assisted transfers, this is the session identifier that is required to help the switch merge in the correct call.

## Response `202`

- SuccessResponse
  - `code` integer, required
  - `message` string, required

## Other responses

- `400`
- `401`
- `404`

---

[API](https://skmtc.dev/ns-api/apis/netsapiens-api-v2.md) · [All operations](https://skmtc.dev/ns-api/apis/netsapiens-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/ns-api/netsapiens-api-v2/revisions/d37f65b5b886/schema)