Getting Started with the Noise Remover Website API
The website API is a server-to-server workflow for submitting a file and checking an asynchronous job. It is separate from the mobile API v2 and from the Studio’s paid chunk-upload route. This guide is an integration plan, not a claim that a new live job was run for this draft.
Check access and keep credentials server-side
Confirm the API plan and generate or manage keys through the account dashboard. Treat a key as a secret: store it in a protected server environment or secret manager, not a browser bundle, public repository, URL or chat. Do not print request headers or signed download links in logs.
Use the exact current API reference for authentication and response fields. A website API key is not interchangeable with a mobile session token.
Submit one permitted file
The website submit route is POST /api/v1/external/enhance. It accepts multipart form data with file, and supports preset and output_format subject to entitlement. Presets include auto, podcast, video, call, voiceover and music. Let the HTTP library create the multipart boundary.
The inspected direct-upload backend ceiling is 200 MB, with a 60-minute per-file API-plan limit. Upstream proxies may impose a smaller request limit. Do not advertise this endpoint as the 1 GB Studio chunk route.
Persist the job reference and poll with limits
After an accepted submission, persist the returned job reference with your own task record. Use GET /api/v1/external/job/:job_id to check status. Respect rate-limit responses and use bounded polling with a deadline and backoff rather than an infinite tight loop.
Handle completion and failure separately. An HTTP success on submission means the job was accepted, not that an output already exists. Validate the response envelope against the current reference before writing a parser.
Download before expiry and validate the result
Use the result URL supplied for the authorised job; do not invent a URL from an ID or forward your API key to an unrelated host. Treat temporary URLs as sensitive. Save the output to your own intended destination before the displayed expiry.
Check status, expected media type, actual size and playback. For video, check duration and sync. Expiring access is not a guarantee of physical deletion from every storage or backup at the exact expiry instant.
Make failure visible
Separate validation errors, quota restrictions, rate limiting and transient transport failures. A timeout after a submit can be ambiguous: do not blindly repeat it as if nothing happened. Record a safe correlation ID and investigate the job state. Keep passwords, keys, recording content and tokens out of logs.
Start with a non-sensitive file you own in an approved test environment before enabling production integration. See the automation design checklist for retries and usage control.
Your next step
Keep the original, check the current allowance and compare the words as well as the background.
Open Studio · Check file and plan limits · Ask a product question