Use the webhook_id returned from a previous GET, POST or PUT response to retrieve the webhook configuration.

Use the job_id returned from a previous POST response
to check on the status of an asynchronous request.

Use the job_id returned from a previous POST response to check on the status of an asynchronous request.

Use the job_id returned from a previous POST request to check on the status of an asynchronous job.

Query jobs that were submitted at or after the specified date and time (inclusive).

Query jobs that were submitted at or before the specified date and time (inclusive). The submitted_before must be the same or later than submitted_after.

Query jobs that have the specified status.

Used when querying the next page of jobs. Specify the next_token that was returned in the previous call.

The url should be in the form dlb://object-key where the object-key can be any alpha-numeric string. The object-key is unique to your account API Key so there is no risk
of collision with other users.

The callback url that will be called when job execution completes

Use the webhook_id returned from a previous GET, POST or PUT response to retrieve webhook configuration.

Specify the location for a media file. You can specify either a string URI or an object containing the URI and authentication parameters appropriate for your cloud storage solution.

Specify the location for a file. You can specify either a simple string URI or an object containing the URI and authentication parameters depending on your cloud storage solution. See Media Input and Output for a more detailed description of all the options.

Specify the location for an input media file. You can specify either a simple string URI or an object containing the URI and authentication parameters depending on your cloud storage solution. See Media Input and Output for a more detailed description of all the options.

The type or category that best describes the media content.

The threshold (in dBFS) that defines silent audio sections.

The minimum duration (in seconds) that defines a silent section.

Specify the location for an input media file as a URL.

Specify the location for a media file. You can specify either a single string or an object with authentication parameters depending on your cloud storage solution.

Learn more in the documentation about Media Input and Output options with cloud storage providers.

The type or category that best describes the media content. Each of the available types is listed below with a few typical observations about the type of recording environment.

If not specified, the algorithm will choose the processing that is an estimated best fit.

A list of different inputs to be mastered by the Music Mastering API.

Controls the amount of dynamic EQ processing applied to the music track.

The integrated loudness target level. Measured in loudness units relative to full scale (LUFS).

The url should be in the form dlb://object-key where the object-key can be any alpha-numeric string. The
object-key is unique to your account API Key so there is no risk of collision with other users.

List of input files to be transcoded.

If more than one file is provided, the list of inputs will be stitched in the order provided to each output.

The location for a media file. You can specify a string such as one of the following options:

A world readable http location
A pre-signed URL for popular cloud storage providers such as S3, GCP, etc.

A list of different outputs that can be generated by the Transcode API

The callback url that will be called when job execution completes.

Dolby.io offers support for media workflows to analyze and enhance file-based media and improve the quality of audience experiences.

Zapier Automation Platform

PRODUCTS

CAPABILITIES

By use case

By app

By team

By company size

How Zapier Zaps

How Zapier Uses AI

By team

Learn more

Get help

Zapier quick-start guide

Developer resources

Dolby.io Integrations

Dolby.io Help & Support

How to Get Started with Dolby.io on Zapier

About Dolby.io

Related categories