---
title: "Add sound via file"
method: POST
path: "/campaigns/sounds/files"
tags: ["campaigns"]
---

# Add sound via file

`POST /campaigns/sounds/files`

Create a campaign sound file via a supplied .mp3 or .wav file

## Query parameters

- `fields` string

## Response `200`

successful operation

- CampaignSound — Represents a sound recording from account's sound library which can be used in different API operations
  - `id` integer — An id of a sound file
  - `name` string — A name of a sound file
  - `created` integer — The time when the given resource was created, formatted in unix time milliseconds (read only). Example: 1473781817000 for Sat, 05 Jan 1985 14:03:37 GMT
  - `lengthInSeconds` integer — Length of a sound in seconds
  - `status` 'UPLOAD' | 'RECORDING' | 'ACTIVE' | 'ACTIVE_SYSTEM' | 'FAILED' | 'ARCHIVED' | 'SCRUBBED' — A current status of a sound, available values: UPLOAD - uploading is in progress, RECORDING - recording of sound is in progress, ACTIVE - sound is ready, FAILED, ARCHIVED - sound was archived, SCRUBBED - sound was scrubbed
  - `duplicate` boolean — True if the same sound file exists in a sound library of account

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not found
- `500` — Internal Server Error

---

[API](https://skmtc.dev/callfire/apis/callfire-api-documentation.md) · [All operations](https://skmtc.dev/callfire/apis/callfire-api-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/callfire/callfire-api-documentation/revisions/9f6fb501bc03/schema)