Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
284 lines (223 sloc) 9.31 KB

This document describes how to make requests via the "v1 API" that shipped for early Loudr partners. For new integrations, please see Loudr's Web API documentation at

Although this format is not the most current release, Loudr has no plans to discontinue support for these specifications.

Making a Request

Send a POST request to /v1/sound_recording/request_license with a JSON body described by request-single.json in this repository.

You may also send bulk request files. Click here to learn more.


Sample Post Data

  "title": "Track Title",           /* required */
  "artist": "Track Artist",         /* required */
  "length": 120,                    /* required */
  "album": "Album Title",           /* required */
  "isrc": "US-S1Z-99-00001",
  "upc": "840218195668",
  "label": "Label Name",
  "release_date": "2015-01-01",
  "licensor": "Licensor of Content",
  "compositions": [
      /* title is required, as well as one or more of an author or composer */
      "title": "Original Song Title",
      "artist": "Original Artist",
      "composer": "Original Composer",
      "author": ["Original Song Writer 1", "Original Song Writer 2"],
      "album": "Optional Source Album",
      "source": "Optional Source Material (film or video game title, etc)",
      "link": "Optional URL to Original Song (YouTube, etc)",
      "iswc": "International Standard Musical Work Code",
      "notes": "Any Additional Research Notes (Optional)"
  "metadata": {
      /* this is a custom object you may use */
      "publisher": "Optional known publisher if present"
  "licenses": {
    "stream": "continuous",
  "vendor_id": "Unique ID of this record in your system - if None provided, ISRC is used",

Request Fields

Any of the following fields which aren't explicitly required may be required depending on your business agreement with Loudr.

    `str` Required.
    Title of track or sound recording being licensed.
    `str` Required.
    Original performing artist(s).
    `int` Required.
    Length in seconds. Round up to the nearest whole second.
    `str` Required.
    Name of the album this request was or will be released on.
    ISRC of request.
    UPC of the album.
    ISRC of request.
    ISO formatted date this content will be or was released. `YYYY-MM-DD`.
    Name of the original licensor of content.
    `object` Required.
    Describes the configurations of licenses requested, as well as units.
    See the "Licenses (Configurations)" section below.

Vendor ID, and a note on IDs

The vendor_id property is used to directly associate our records with yours. If you omit this field, which is valid, we will use the ISRC as the unique ID.

    An ID you may specify to retain your database ID for a given request.

Licenses (Configurations)

The licenses property defines what kind of licenses you are requesting, and in what quantity.

To specify licensing for digital downloads with continuous reporting (instead of a fixed quantity):

    "licenses": {
      "download": "continuous",

To specify licensing for interactive streams with continuous reporting (instead of a fixed quantity):

    "licenses": {
      "stream": "continuous",

A full list of acceptable types exists in

Compositions (Songs being Covered - what we're licensing)

Depending on your business agreement with Loudr, you may leave compositions empty if you do not know exactly what has been covered. If you do know, it is always better to tell us - as providing this information greatly decreases the amount of time it takes to process and fulfill a license.

Properties for each composition:

All fields may be a single string or list of strings (except for 'notes' and 'iswc').

    `str` Required.
    Composition title. Provide multiple titles if the composition may have alternate names (or in alternate languages).
    Original performing artist(s).
    Original composer(s).
    (Either one composer or one author is required)
    Original author(s) of the song. Authors and composers may overlap,
    if so, they only need to be mentioned once.
    (Either one composer or one author is required)
    Original album the song was released on, if any.
    Original source material. Such as a movie or video game title.
    URL to the source material.
    International Standard Musical Work Code.
    (Only a single string)
    Any additional notes to aid composition search.
    (Only a string).

Note: if publisher information is known, it should provided in the metadata object at the top level of the request.

Prior Licenses

When requesting licenses for content (sound recording) that has been previously released (and licensed), we must know the dates and configurations that were captured in the past.

The prior_licenses field describes prior licenses obtained for a fixed quantity license.

It must include each configuration previously purchased, and the release date specified on the original license.

prior_licenses is only expected for fixed quantity licenses.


  "prior_licenses": {
    "dpd": "2015-01-01",
    "stream": "2015-01-01"

Requests which have been previously licensed

Send previously licensed requests in the same format as above, with the following additional information in the previous_license object:

"previous_license": {
  "license_id": "123456789", /* previous license ID from other partner - REQUIRED */
  "partner": "Licensing Agent", /* Name of previous partner coordinated with - REQUIRED (Please inquire with us what code to use for your previous partner) */
  "publisher_ids": ["P1234"], /* List of Previous partners worked with - OPTIONAL */

See a full example: request-single-previously-licensed.json.


The _secret property is your secret token. It enables you to make and view requests on behalf of your client account (creator/some-id).

This secret token works much like an OAuth2 access grant, so don't share it or lose it.


A status code between of 200 will signify a valid response.

We recommend clients utilize the response from the recording GET endpoint to fetch and validate their requst.

The response is a JSON object that provides:

  "_message": null,
  "_single": "sound_recording",
  "sound_recording": {
    "_fb": true,
    "_js_kind": "Sound_Recording",
    "_kind": "sound_recording",
    "_permissions": [
    "_uri": "sound_recording/creator/xxx--abc123",
    "album": "El Diablo De Culiacan",
    "artist": "Atomo",
    "created_ago": null,
    "created_at": null,
    "earliest_clearance_at": null,
    "is_hard_rejection": false,
    "isrc": "USE7D0900003",
    "label": "Del Records",
    "length": 192,
    "license_fulfilled": false,
    "license_fulfilled_at": null,
    "license_status": 2,
    "license_status_str": "In Progress",
    "p_id": "creator/xxx--USE7D0900003",
    "p_key": "agxkZXZ-cmRzY292ZXJyMQsSEFJkU291bmRSZWNvcmRpbmciG2NyZWF0b3IvN2NTZEQtLVVTRTdEMDkwMDAwMww",
    "partner": "creator/xxx",
    "partner_recording_id": "abc123",
    "release_date": null,
    "title": "5.7",
    "upc": "705105796444",
    "updated_at": "2015-06-15T22:37:00.156993",
    "vendor_album_id": ""

(You may see a lot more detail then this, but you only need response['sound_recording']['_uri'] for now.)

You will use the URI to retrieve status updates, match streamed API results to your content, and include in your usage reports.

Retrieving Requests

It is highly recommended that all clients integrate with Loudr using the Version 2 API, click here for details.

Version 1 response details remain available here.

Sending Bulk Requests

For large deliveries of bulk requests, you may choose to send them over SFTP or Email.

JSON [preferred method]

With a bulk upload, we expect a JSON file with one line per recording. See the example requests-bulk.json.


While we prefer the JSON format, you may also create a CSV to export your requests. See the example requests-bulk.csv. Multiple artists and authors should be denoted with the SEMICOLON character, and all fields containing commas may be wrapped in quotes ("). (See request 2 in the above example.) As a rule, UPCs are best formatted as strings (and presented in quotes), to prevent modern editors from reading scientific notation.


"Here’s a ""quote"" in a field"

will appear as

Here's a "quote" in a field