Getting Started with the noise-remover.com API

The noise-remover.com API lets you integrate professional AI noise removal directly into your application, workflow automation, or platform. Whether you are building a transcription service, a podcast hosting platform, a customer service call recording system, or a video production pipeline, the API gives you the same noise removal and voice enhancement quality available in the Studio — accessible programmatically at scale.

This guide covers everything from getting your first API key to making successful API calls and handling responses — with working code examples in multiple languages.

Who the API is for

The noise-remover.com API is designed for developers and technical teams who need to:

• Process audio files automatically as part of a larger workflow
• Batch-process large numbers of recordings without manual intervention
• Integrate noise removal into a SaaS product as a feature for their end users
• Build automation that triggers noise removal based on events (new Zoom recording uploaded, customer call completed, etc.)

Getting your API key

To access the API, you need one of the API plans: Dev ($19/mo — 1,500 minutes), Pro API ($49/mo — 4,000 minutes), or Business ($99/mo — 10,000 minutes). Subscribe on the pricing page, then find your API key in your dashboard under the API Keys section.

Your API key authenticates every request. Include it as a Bearer token in the Authorization header of every API call. Never expose your API key in client-side code or public repositories.

Your first API call

The core endpoint is POST /api/external/enhance. It accepts a multipart form upload with your audio or video file, the preset to use, and the desired output format. Here is a working example in three languages:

cURL:

curl -X POST https://api.noise-remover.com/api/external/enhance   -H "Authorization: Bearer YOUR_API_KEY"   -F "file=@/path/to/your/audio.mp3"   -F "preset=auto"   -F "output_format=wav"

Node.js (with node-fetch and form-data):

const FormData = require('form-data');
const fetch = require('node-fetch');
const fs = require('fs');

const form = new FormData();
form.append('file', fs.createReadStream('./audio.mp3'));
form.append('preset', 'auto');
form.append('output_format', 'wav');

const response = await fetch('https://api.noise-remover.com/api/external/enhance', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    ...form.getHeaders()
  },
  body: form
});

const result = await response.json();
console.log('Job ID:', result.job_id);

Python (with requests):

import requests

with open('audio.mp3', 'rb') as f:
    response = requests.post(
        'https://api.noise-remover.com/api/external/enhance',
        headers={'Authorization': 'Bearer YOUR_API_KEY'},
        files={'file': f},
        data={'preset': 'auto', 'output_format': 'wav'}
    )

result = response.json()
job_id = result['job_id']
print(f'Job ID: {job_id}')

The response includes a job_id that you use to check the status of the processing job.

Polling for job completion

Processing is asynchronous. After submitting a file, poll the job status endpoint until the job status is completed or failed:

GET /api/external/job/:job_id
Authorization: Bearer YOUR_API_KEY

The response includes the job status (pending, processing, completed, failed), progress percentage, and on completion, a download URL for the processed file. Poll every 3-5 seconds — avoid polling more frequently than this to stay within rate limits.

Pro API and Business plan subscribers can configure webhooks instead of polling. Add your webhook URL in the dashboard and we will POST a notification to your endpoint when each job completes, including the download URL and job metadata.

Best practices for production use

Implement retry logic for failed jobs — network issues can occasionally cause transient failures that succeed on a second attempt. Set up low-balance alerts in your dashboard to avoid service interruption when approaching your monthly limit. Store processed audio files immediately on download — the download URL expires after 1 hour. Log job IDs and correlate them with your own records for debugging and audit purposes.

For high-volume use cases (thousands of files per day), contact business@noise-remover.com to discuss Enterprise plans with custom limits, dedicated infrastructure, and SLA guarantees.