Read the artist, not a copy.

Every app that works with artists keeps its own copy of the same bio, photos and contacts, and every copy goes stale. Read the artist's profile instead: verified by TAP, kept current by the artist and its team.

What a partner can do

Read, sign in, write.

Or all three. The artist decides what you may touch.

Read

Read an artist. One request returns the profile, with the date it was verified. As the signed-in person, or server to server.

Sign in with TAP

Sign people in. Sign in with TAP tells you who the person is and which artists they belong to, with their role in each.

Write

Write to an artist. An app TAP has granted the capability can create the profile for an artist it holds, edit it from inside the app, and publish it. Every write is logged.

Contacts

Find the right person. Booking, press, management: the artist says who handles what, so a request lands with the person who answers it.

The first partner

Stagent, the first partner.

Stagent is booking software for agencies and artists. It moved the EPKs of its artists into TAP, where each artist owns the result: the agency works on the artist from Stagent, and the artist signs in to Stagent with TAP.

A promoter who books through Stagent opens the profile the artist keeps, not a copy the agency keeps for them.

One change

What your app sees, a second later.

Sam changes the bio at 14:02. Your app holds no copy, so there is nothing to refresh: the next request is the new version.

  1. 14:02:10 The editor Sam saves the bio. One field, one profile.
  2. 14:02:10 The API The ETag moves from "8f3a1c" to "b21e07". The next GET returns the new bio; a request with the old ETag no longer answers 304.
  3. 14:02:10 The website The next visitor reads the new bio under the hero.
  4. 14:02:10 The EPK Copy copies the new bio. The download carries it too.
  5. 14:02:11 Your app Reads the artist on its next request and shows the new bio. Nothing to sync, nothing to store.
  6. 14:02:11 A webhook artist.updated to every app that asked to be told. Coming soon; first on the list below.
  7. 14:02:11 The activity log Sam changed the bio, logged for the artist's team.
Who reads an artist

Who reads an artist.

Anyone who needs the facts of an artist, from the artist.

Booking software
Bring the roster, sign the agency in, and let the artist own its profile.
Festivals and ticketing
The current bio, photo and contacts for every artist on the bill, from the artist itself.
Streaming and directories
One verified source for the facts every listing repeats.
DJ software
Know which verified person is behind an artist name.
Rights organisations
A performance reported against a verified person, not a spelling of a name.
Press
The EPK, from the artist, current on the day you open it.
Coming soon

Coming soon.

The order TAP builds in. It moves with the partners who need it.

Be told when it changes A webhook when an artist you read is edited, so you stop polling for a change that is not there.
Look up by identifier Give an IPI, ISNI or Spotify ID and get the artist back. The link from a name in a tracklist to a verified artist.
Vouch for an artist A partner that holds the artist confirms it, and that helps the verification check.
Prove presence The passport at the door: who the person is and their role in the artist, readable without a connection.
Report a performance Bookings, slots and sets played, delivered by the partner who captured them and read by the organisation that pays out. The artist stays the owner of what is reported in its name.
The API

Read an artist in one request.

Apps read artists over HTTP with an OAuth token. Nothing to install, no library to keep up with. Two reads, both under artists:read.

GET /api/v1/artists

The artists the signed-in person is a member of, with their permission on each.

Token
A user token from Sign in with TAP, or a personal token.
Scope
artists:read
Parameters
None.
Returns
A list of artists. Each carries permission: what the person may do on it.

GET /api/v1/artists/{identifier}

One artist, by handle or by artist number. Name, facts, intro, bio, photos, logos, riders, releases, channels, contacts, and the date it was verified.

Token
A user token, a personal token, or a client-credentials token from an approved app.
Scope
artists:read
Headers
If-None-Match with the ETag you were given. An unchanged artist answers 304 with no body.
Cache
Private, max-age 60. The ETag changes when the artist changes.
Returns
The artist. Riders stream through TAP; every other file carries a direct URL.

Your first artist, in three requests.

Register the app, get a token, read an artist.

  1. 1 Register an app From your account, under Developers. TAP reviews it; until then the consent screen refuses and the token endpoint issues nothing an artist can be read with.
  2. 2 Get a token Client credentials for reading published artists with no person present. Tokens live a day; a refresh token from the sign-in flow lives 30 days.
  3. 3 Read an artist Send the token as a bearer. Keep the ETag; send it back next time and a 304 costs you nothing to parse.

Every status code, the scopes and personal tokens are in the developer docs.

What it costs

Free for artists. Metered for partners.

Artists never pay. Apps pay by the volume of requests they make, and nothing switches off when you cross into the next band. How the meter works.

Band 1 Free Small volumes. Most apps never leave this band.
Band 2 A plan Large volumes. Sized to the requests you make.
Band 3 Talk to us Reading artists at scale, or a roster to bring. Write first.

Where one band ends and the next begins is settled with the first partners.

Artists

Free for artists.

The handle, the pages, your team and verification. No card, no plan, no watermark.

Partners

Metered for partners.

Register an app from your account and TAP reviews it. Building at scale? Write to hello@tap.fm first.