Skip to main content

Using the International Standard Name Identifier (ISNI) in FUGA

  • Updated

Introduction

This article explains how to add and manage the International Standard Name Identifier (ISNI) within the FUGA Interface. Using ISNI helps reduce mismatches on Digital Service Providers (DSPs) by uniquely identifying artists and contributors. This improves metadata integrity, delivery accuracy, and discoverability across platforms.

 

Overview of ISNI

The International Standard Name Identifier (ISNI) is a globally recognized 16-character code used to identify individuals or organizations involved in creative content. In the music industry, ISNIs are used to disambiguate artists and contributors who may share similar names, ensuring their works are accurately mapped across DSPs.

Using ISNIs in your FUGA catalog provides the following benefits:

  • Minimizes profile mismatches on DSPs
  • Enhances discoverability of releases
  • Unifies identity management with a single identifier across platforms

Although ISNIs are not mandatory for delivery, they are supported by most major DSPs and strongly recommended.

 

Supported DSPs

ISNI delivery is supported by all DSPs receiving DDEX ERN version 3 and higher, including:

  • Spotify
  • Apple Music (prefers Apple IDs but accepts ISNI)
  • YouTube
  • Amazon Music
  • Facebook
  • TIDAL

Note: Apple Music continues to prioritize Apple IDs, so you should continue including Apple IDs in deliveries where available.

 

Adding ISNI in the FUGA Interface

You can assign an ISNI to any artist or contributor via the FUGA interface:

For Artists:

  1. Navigate to Catalog > Artists.
  2. Select the relevant artist profile.
  3. Click the ISNI field in the top-right of the Artist Overview.
  4. Enter the 16-character ISNI.
  5. Save changes.

For Contributors (People):

  1. Navigate to Catalog > People.
  2. Select the contributor profile.
  3. Enter the ISNI in the field beneath the contributor’s name.
  4. Save changes.

During Artist Creation:

  • When creating a new artist profile, the FUGA Interface will prompt you to enter an ISNI before saving.

 

Assigning ISNI via Extensible Markup Language (XML)

FUGA XML:

  • Use the <isni> node to assign an ISNI to an artist or contributor.

DDEX XML:

  • Use <PartyId IsISNI="true"> under one of the following:
    • DisplayArtist
    • ResourceContributor
    • IndirectResourceContributor

Important: FUGA only supports one ISNI per artist or contributor. If multiple ISNIs are present in a DDEX file, the delivery will be rejected.

 

Validation Rules in FUGA

FUGA performs the following validations when ISNIs are added:

  • Format Compliance: Must be 16 characters with the final character being a digit or the letter "X".
  • Single ISNI Per Entity: Only one ISNI is allowed per artist or contributor in FUGA.

Not validated in FUGA:

  • Name match against the official ISNI database.
  • ISNI uniqueness across your catalog. The same ISNI can be used for different entities within your account.

 

Obtaining and Searching for an ISNI

  • To check if an ISNI already exists for an artist or contributor, search the public ISNI database.
  • To request a new ISNI, contact an ISNI Registration Agency. These organizations are authorized to issue ISNIs.

 

FAQs and Notes

Is ISNI delivery mandatory? No. DSPs that support ISNI also continue to accept standard artist identifiers such as Spotify Artist URIs or Apple IDs.

Can a SubAccount assign ISNIs? Yes. SubAccounts can assign ISNIs to artists and contributors associated with their own catalog.

What if an artist doesn’t have an ISNI? You may:

  • Request one via a registration agency
  • Continue using DSP-specific identifiers for Spotify, Apple Music, Audiomack, and SoundCloud

Can I assign multiple ISNIs to one artist or contributor? No. FUGA only supports a single ISNI per artist or person.

 

 

Need Help? Contact your FUGA representative or reach out via our support channel at support@fuga.com.

 

Related articles