Reverse ID Lookup
Why reverse ID lookup
Most teams already have third-party IDs lying around their database — a Spotify artist URI on a "follow" row, a ticketmaster: event id from a webhook, a MusicBrainz MBID inside a fan profile, a SeatGeek venue id on a saved seat. JamBase Data turns any of those into the matching JBD record in a single request. No mapping table to maintain, no fuzzy name matching, no separate enrichment service.
The URL pattern
Every reverse-lookup endpoint follows the same shape — replace {family} with one of events, artists, venues, or streams:
GET https://api.data.jambase.com/v3/{family}/id/{source}:{id}
{source} is the slug of the third-party system whose id you hold (or jambase for a JBD id). {id} is the raw identifier from that system. The response is the same Schema.org-aligned object the corresponding search endpoint returns, so downstream parsing is identical.
Examples by source
Copy-paste curl per source family. All four work on every plan, including the free Developer tier.
Spotify URI → JBD artist
curl "https://api.data.jambase.com/v3/artists/id/spotify:3WrFJ7ztbogyGnTHbHJFl2?expandUpcomingEvents=true" \-H "Authorization: Bearer YOUR_API_KEY"
Ticketmaster event ID → JBD event
curl "https://api.data.jambase.com/v3/events/id/ticketmaster:G5vYZ4ZpZAfdJ" \-H "Authorization: Bearer YOUR_API_KEY"
MusicBrainz MBID → JBD artist
curl "https://api.data.jambase.com/v3/artists/id/musicbrainz:e2305342-0bde-4a2c-aed0-4b88694834de?expandUpcomingEvents=true" \-H "Authorization: Bearer YOUR_API_KEY"
SeatGeek venue ID → JBD venue
curl "https://api.data.jambase.com/v3/venues/id/seatgeek:18?expandUpcomingEvents=true" \-H "Authorization: Bearer YOUR_API_KEY"
Discovering valid sources
Four lookup endpoints return the canonical slug list per family — call once, cache, and use the slugs verbatim in the path.
| Family | Slugs endpoint |
|---|---|
| Events | GET /v3/lookups/event-data-sources |
| Artists | GET /v3/lookups/artist-data-sources |
| Venues | GET /v3/lookups/venue-data-sources |
| Streams | GET /v3/lookups/stream-data-sources |
Today's allow-list spans Spotify, MusicBrainz, Ticketmaster, SeatGeek, AXS, Eventbrite, DICE, Etix, Seated, See Tickets, Sofar Sounds, SuiteHop, Tixr, and Viagogo — plus jambase for native JBD identifiers. The slug lists evolve, so prefer the lookup endpoints over hard-coding.
Same capability via MCP
The hosted MCP server at data.jambase.com/mcp exposes the same reverse-ID bridge to AI agents.
Tools getEvent, getArtist, getVenue, and getStream all accept a single identifier argument shaped as {source}:{id}, so an agent that already holds a Spotify URI from chat history can resolve to the JBD object without an intermediate searchArtists call. See the MCP guide for install instructions.
Plan & entitlement
Reverse ID lookup works on every plan.
Lookups by any supported source slug (Spotify, Ticketmaster, MusicBrainz, SeatGeek, the rest of the allow-list, and jambase) work on every plan, including the free Developer tier and Trial. Each lookup counts against your normal monthly request quota, like any other call.
Returning third-party IDs and links inside responses is a separate feature. The expandExternalIdentifiers and expandArtistSameAs expansions require Startup or higher, or an active Trial. See pricing for tier details.