Bandsintown API
★ Only Publicly Available OpenAPI DocumentMediaContent DeliveryapiKey2 EndpointsREST
For Agents
Look up artist profiles and tour events on Bandsintown, filtered by upcoming, past, or a specific date range.
Use for: Get the upcoming tour dates for a specific artist, Retrieve an artist's Bandsintown profile and tracker count, Find all events for an artist between two specific dates, List past tour events for an artist for a year-in-review post
Not supported: Does not handle ticket purchases, fan account management, or write operations on artist data — use for read-only artist info and event lookups only.
The Bandsintown API gives artists and the enterprises representing them read-only access to artist information and tour events on Bandsintown. The two endpoints return the artist's profile (Bandsintown page link, photo, tracker count, MBID, Facebook page) and the artist's events (date, venue, location, lineup, ticket links). Event lookups can be filtered to upcoming, past, all, or a specific date range. An app_id query parameter is required and is granted on request after accepting Bandsintown's Terms and Conditions.
Install Jentic One Beta
Connect the Bandsintown API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bandsintown API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Bandsintown API.
Look up an artist's Bandsintown profile, photo, and current tracker count
Retrieve upcoming tour events for an artist with venue, datetime, and ticket links
Filter event results to past, all, upcoming, or a specific date range
Surface lineup details (support acts, festival co-headliners) attached to each event
Use Cases
Patterns agents use Bandsintown API for, with concrete tasks.
★ Artist Website Tour Widget
Artists and labels embed a tour-dates widget on their official website by calling GET /artists/{artistname}/events with date_range=upcoming. The response gives venue, city, datetime, and ticket links per event, ready to render as a list. Updates flow automatically when the artist's team adds events to Bandsintown, so the site stays in sync without manual edits.
Call GET /artists/Beyonce/events?app_id={app_id}&date=upcoming and render the upcoming tour dates as a list with city, venue, and ticket link.
Fan Newsletter Personalisation
Send fans a personalised newsletter showing only the tour dates relevant to their city by combining Bandsintown's events feed with a fan-location segment. Pull events with /artists/{artistname}/events for each artist the fan tracks, filter by city in your application, and inject the matched events into the newsletter template.
For each tracked artist, fetch GET /artists/{artistname}/events?app_id={app_id}&date=upcoming, filter to events in the fan's city, and merge into the newsletter.
Year-in-Review Content
Build a year-in-review post by pulling all past events with /artists/{artistname}/events?date=past for a given artist and bucketing them by month and country. The response includes venue, city, country, and lineup, which is enough to assemble a touring summary without scraping or maintaining a separate calendar.
Fetch GET /artists/{artistname}/events?app_id={app_id}&date=past, group results by month, and produce a count of shows and unique cities visited.
AI Agent Integration via Jentic
An agent built on Jentic can answer fan questions like 'when is X playing in Y' by hitting Bandsintown for the artist's upcoming events and filtering by city. Because the API requires only an app_id, Jentic stores it in MAXsystem so the agent calls the operation without handling the credential directly.
Search Jentic for 'get artist tour dates', load the schema for GET /artists/{artistname}/events, and execute it with artist=Phoebe Bridgers and date=upcoming.
Key Endpoints
2 endpoints — the bandsintown api gives artists and the enterprises representing them read-only access to artist information and tour events on bandsintown.
METHOD
PATH
DESCRIPTION
GET
/artists/{artistname}
Get artist profile information
GET
/artists/{artistname}/events
Get upcoming, past, all, or date-range artist events
GET
/artists/{artistname}
Get artist profile information
GET
/artists/{artistname}/events
Get upcoming, past, all, or date-range artist events
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Bandsintown app_id is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped operation handles; the raw app_id never enters agent context or logs.
Intent-based discovery
Agents search Jentic with intents like 'get artist tour dates' and Jentic returns the matching Bandsintown events operation with its date and date_range parameters, so the agent skips reading docs.
Time to first call
Direct Bandsintown integration: 1-2 hours once the app_id is granted, mostly response parsing. Through Jentic: minutes — search, load schema, execute. The app_id approval process is the dominant cost in either case.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Bandsintown API through Jentic.
What authentication does the Bandsintown API use?
Each request includes an app_id query parameter (an apiKey). The app_id is granted by Bandsintown after you accept their Terms and Conditions; contact help.bandsintown.com to request one. Through Jentic, the app_id is held in the encrypted vault and injected at execution so the agent never sees it.
Can I get an artist's past tour dates with the Bandsintown API?
Yes. Call GET /artists/{artistname}/events with the date query parameter set to past. The same endpoint accepts upcoming, all, or a specific date range expressed as YYYY-MM-DD,YYYY-MM-DD.
What are the rate limits for the Bandsintown API?
Specific rate limits are not declared in the OpenAPI spec; Bandsintown enforces limits per app_id and use case. Cache responses where possible and contact Bandsintown support before high-volume scraping or sync workloads.
How do I retrieve an artist's upcoming events through Jentic?
Search Jentic for 'get artist tour dates', load the schema for GET /artists/{artistname}/events, and execute it with the artist name and date=upcoming. Jentic injects the app_id at execution so the agent does not need to manage it.
Is the Bandsintown API free?
Use of the Bandsintown API requires written consent from Bandsintown and acceptance of their Terms and Conditions. There is no published self-serve paid tier; access is granted per applicant. Check http://help.bandsintown.com/ for the current process.
GET STARTED