Cleaning music reference links before a VJ project handoff

Project disclosure: this is an update about FunDownloader, the tool being shared here. We have released a free, keyless Link API for validating and canonicalizing supported Spotify, Instagram and Twitter/X links.

A cleaner reference sheet

For an audiovisual project handoff, keep reference links separate from the audio and video files you have cleared for use. A useful sheet has columns for reference URL, canonical URL, creative notes, asset filename, and permission status.

Normalization helps when the same reference arrives through several sharing links. Removing tracking parameters makes those links easier to compare. It does not establish that two different posts contain the same media.

Try the endpoint

Send a GET request to https://fundownloader.online/api/v1/link with a URL-encoded url parameter and an optional platform parameter: spotify, instagram, or twitter. Spotify is the default. Input is limited to 512 characters.

Example request:

https://fundownloader.online/api/v1/link?platform=spotify&url=https%3A%2F%2Fopen.spotify.com%2Ftrack%2F4uLU6hMCjMI75M1A2tKUQC

The example demonstrates a link format; it does not claim that the referenced track is currently available.

A valid format returns HTTP 200 with the canonical URL, content identifier, platform and type. Unsupported or invalid input returns HTTP 400 with an error message. The endpoint supports Spotify tracks/playlists, Instagram posts/reels, and Twitter/X status links.

What a successful check means

The response includes availabilityChecked: false. Processing is limited to parsing the URL: it does not request the post, inspect media, download anything, or check content rights. In a project tracker, label the result as a normalized reference rather than a verified performance asset.

Keep a separate review step for whether the reference is accessible and whether you have permission for the intended use. Store the cleared file and its permission record with the production materials.

The API requires no key and supports browser requests through CORS. Successful responses may be cached for one hour; service availability is best-effort.

API documentation and curl example · FunDownloader

This is a small utility for teams passing around reference links in briefs and cue sheets. The creative decisions and asset permissions still belong in the production workflow.