Audome API

Name: Audome API API
Brand: Audome API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaAudio Processingbearer12 EndpointsREST

For Agents

Authenticate against an Audome workspace, create projects, upload audio files, and manage the tag lists used to describe them via Bearer tokens.

Quickstart

Get started with Audome API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"upload an audio file to Audome"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Audome API API.

Authenticate a workspace user via POST /authenticate to obtain a Bearer token

Invalidate a session via POST /logout when an automation completes

Create a new project for an audio engagement with POST /projects

Upload an audio file to a project via POST /projects/{projectUuid}/files

List, read, update, and delete tag lists used to describe audio assets

GET STARTED

Start building with Audome API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Audome API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Audome API, keeping it validated and agent-ready. Audome is a workspace for audio teams that want to organise raw audio, project files, and the tag taxonomy used to describe them. The API exposes authentication, projects, file upload, and tag-list management so an external tool can ingest audio into an Audome workspace, attach the right tags, and read the project state back without using the web UI. With 12 endpoints it covers the full lifecycle of a project plus tag governance.

Use Cases

Patterns agents use Audome API API for, with concrete tasks.

★ Automated audio ingestion from a DAW or studio rig

Studios that record many sessions per week want raw audio to land in Audome the moment it is rendered. An ingestion script authenticates via POST /authenticate, creates a project per session via POST /projects, and uploads each rendered file via POST /projects/{projectUuid}/files. Files arrive in Audome organised by project without an engineer dragging them through the web UI.

Authenticate via POST /authenticate, create a project named 'Session 2026-06-09' via POST /projects, then POST /projects/{projectUuid}/files with the rendered WAV.

Tag taxonomy governance

Audio teams use tag lists to describe sessions consistently. Over time tags drift and duplicates appear. The tag-lists endpoints let an admin script audit the workspace: GET /tag-lists returns the full taxonomy, PATCH /tag-lists/{taglistUuid} renames or merges, and DELETE /tag-lists/{taglistUuid} retires unused lists. POST /tag-lists/{taglistUuid}/tags/{tagUuid} attaches a tag to a list as part of a cleanup pass.

Call GET /tag-lists, identify any list with fewer than two tags attached, and DELETE /tag-lists/{taglistUuid} for each.

Project status reporting

A producer wants a daily report of every active Audome project and how many files are attached to each. GET /projects paginates the workspace's projects, and GET /projects/{uuid} returns the file list per project. The agent assembles a CSV or Slack message with project name, owner, and file count without touching the Audome UI.

Page GET /projects, then for each project call GET /projects/{uuid} and emit a Slack message listing project name and file count.

AI agent integration via Jentic

An audio-ops agent can use Jentic to upload audio into Audome without holding the Bearer token in prompt memory. The agent searches an intent like 'upload an audio file to an Audome project', Jentic returns the matching operation with its input schema, and the call is executed with the token resolved from the Jentic vault. Authentication and refresh are handled by Jentic.

Use Jentic search 'upload audio to Audome', load the schema for POST /projects/{projectUuid}/files, and execute it for a known projectUuid with a multipart audio body.

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for audome api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/authenticate

Authenticate and obtain a Bearer token

POST

/logout

Invalidate a Bearer token

GET

/projects

List projects in the workspace

POST

/projects

Create a new project

GET

/projects/{uuid}

Get a specific project

POST

/projects/{projectUuid}/files

Upload an audio file to a project

GET

/tag-lists

List tag lists

POST

/tag-lists

Create a tag list

POST

/authenticate

Authenticate and obtain a Bearer token

POST

/logout

Invalidate a Bearer token

GET

/projects

List projects in the workspace

POST

/projects

Create a new project

GET

/projects/{uuid}

Get a specific project

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Audome workspace credentials and Bearer tokens are stored encrypted in the Jentic vault. Tokens are refreshed via POST /authenticate when they expire, so the agent never sees the raw token in its context.

Intent-based discovery

Agents search by intent (e.g., 'upload audio to Audome') and Jentic returns the matching operation with its input schema, so the agent picks /projects, /projects/{projectUuid}/files, or /tag-lists without reading the docs portal.

Time to first call

Direct Audome integration: 1 day to wire authentication, multipart upload, and tag-list management. Through Jentic: under 30 minutes from search to first executed call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Auphonic API

Auphonic is the closest peer for automated audio post-production and rendering APIs.

Choose Auphonic when the workflow needs leveling, noise reduction, and rendered output; use Audome for project organisation and tag taxonomy.

Complementary

Dropbox API

Dropbox often sits in front of Audome as the source of raw audio files to ingest.

Choose Dropbox to fetch the source audio; use Audome to land the file in a structured project with tags.

Complementary

Castos API

Castos hosts and distributes podcast episodes once Audome has organised the source audio.

Choose Castos for podcast publishing; use Audome to manage the working files and tags before distribution.

FAQs

Specific to using Audome API API through Jentic.

Why is there no official OpenAPI spec for Audome API?

Audome publishes its API reference at app.audome.com/api-documentation but does not distribute an OpenAPI file. Jentic generates and maintains this spec so that AI agents and developers can call Audome API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Audome API use?

The Audome API uses Bearer token authentication. POST /authenticate exchanges workspace credentials for a Bearer token, which is then sent in the Authorization header on every other request. Through Jentic the credentials and token are stored in the vault and injected at execution time.

Can I upload an audio file to a project with the Audome API?

Yes. POST /projects/{projectUuid}/files accepts a multipart upload and attaches the file to the named project. Create the project first via POST /projects, then upload using the returned projectUuid.

What are the rate limits for the Audome API?

Audome does not publish per-endpoint rate limits in the spec. Production integrations should pace bulk uploads against the file-upload endpoint and back off on 429 responses, which the platform returns when concurrent uploads exceed the workspace limit.

How do I create a project and upload a file through Jentic?

Run jentic search 'create an Audome project', execute POST /projects, then run jentic search 'upload audio to Audome' and execute POST /projects/{projectUuid}/files with the returned projectUuid. Jentic resolves the Bearer token from the vault at execution time.

Is the Audome API free?

API access is included in Audome's standard workspace plans rather than priced per call. A workspace must be on a plan that allows API access for the bearer token issued by /authenticate to be honoured.