---
title: "Update Greeting from Upload (Multipart/Mixed Post)"
method: PUT
path: "/domains/{domain}/users/{user}/greetings/{index}#3"
tags: ["Media/Greetings"]
---

# Update Greeting from Upload (Multipart/Mixed Post)

`PUT /domains/{domain}/users/{user}/greetings/{index}#3`

## Request

- Base URL: `https://ns-api.com/ns-api/v2`
- URL: `https://ns-api.com/ns-api/v2/domains/{domain}/users/{user}/greetings/{index}#3`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/ns-api/apis/netsapiens-api-v2/docs/domains/:domain/users/:user/greetings/:index%233/put.ts> (a function with typed inputs; its response is checked against the schema)

> Note: # and anything after is NOT needed, its just to allow multiple examples for the same path/method.

## 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.
- `index` string, required

## Request body `multipart/form-data`

- object
  - `script` string: This is a simple explanation of what the audio is and can include what is said in the audio file for explanation.
  - `File` string, binary: This is a "File" type parameter that needs to include the audio file in question using a file post method.
  - `convert` string: Setting yes will allow the API to attempt to convert the file from accepted formats into the correct format for media playback
  - `synchronous` string: When synchronous is requested with "yes" the response will be a 200 on success and will contain a valid JSON representiation of the new resource. If no or left off request a 202 "Accepted" will be given in a success case and this can be considered a success. Synchronous responses will be a little slower as the API will process the geo replication request and wait till the local copy has been written and can be read back berfore sending a response.

## Response `202`

- object

## Changes

- **2026-11-03** `bce16087d479`: 3 info
  - removed the non-success response with the status `400`
  - removed the non-success response with the status `401`
  - removed the non-success response with the status `404`

[Operation history](https://skmtc.dev/ns-api/apis/netsapiens-api-v2/changes/domains/:domain/users/:user/greetings/:index%233/put.md)

---

[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.dev/ns-api/apis/netsapiens-api-v2/revisions/bce16087d479?raw)
