canonical: https://jentic.com/apis/bandsintown.com/bandsintown # Bandsintown API 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. ## For AI agents Look up artist profiles and tour events on Bandsintown, filtered by upcoming, past, or a specific date range. ## Scope Does not handle ticket purchases, fan account management, or write operations on artist data - use for read-only artist info and event lookups only. ## Capabilities - 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 ### Artist Website Tour Widget Artists and labels embed a tour-dates widget on their official website by calling GET /artists/{artistname}/events with date=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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance so the agent calls the operation without handling the credential directly. Example prompt: 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 | Method | Path | Description | | --- | --- | --- | | GET | /artists/{artistname} | Get artist profile information | | GET | /artists/{artistname}/events | Get upcoming, past, all, or date-range artist events | ## Key resources - **Artist Info** — Single artist profile including page link, photo, tracker count, and MBID - **Artist Events** — Upcoming, past, all, or date-range event list per artist with venue, location, lineup, and ticket links ## Why Jentic - **Setup:** Wiring Bandsintown by hand means requesting an app_id from Bandsintown, appending it as an apiKey on every request, and handling the read-only artist and event endpoints yourself. Through Jentic you install once, import the Bandsintown API from the API Directory, store the app_id once, and your agent calls it. - **Permission scoping:** Bandsintown puts the artist name in the URL path (/artists/{artistname} and /artists/{artistname}/events), so a rule can pin your agent to one artist: it reads that artist's profile and events and nothing else. You choose the operations it may call, and since this API is read-only there are no write or delete operations to add. - **Credential handling:** Your Bandsintown app_id is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get artist tour dates' or 'look up an artist profile', and Jentic returns the matching Bandsintown operation with its artistname path parameter and optional date filter, so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Songkick API** — Live music event database covering events, venues, artists and locations across 14 endpoints, against Bandsintown's 2 - **Discovery API** — Searches events, attractions and venues across 13 endpoints instead of keying every lookup to one artist name - **SeatGeek API** — Searches live events, venues and performers across 7 endpoints with pricing and popularity data Bandsintown does not return - **setlist.fm API** — Setlist data across 15 endpoints, pairing what was played with Bandsintown's record of where and when ## FAQ ### What authentication does the Bandsintown API use? Each request carries an app_id query parameter (an apiKey), declared as required on both operations in the spec. Bandsintown assigns the app_id after you accept its Terms and Conditions and have written consent from Bandsintown Inc., so access is granted on request rather than by self-serve signup. Through Jentic, your own Jentic One instance holds the app_id encrypted and supplies it at call time, 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? No rate limit is stated in the OpenAPI spec or in Bandsintown's published API documentation, so treat any figure you find elsewhere as unverified. Cache responses where you can, and ask Bandsintown directly before running high-volume or continuous 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? Access is not self-serve. Bandsintown's terms state that to use the API you must read and accept its Terms and Conditions and have written consent from Bandsintown Inc., and that you contact Bandsintown to say what you plan to do and request your personal application ID. No price appears in those terms or in the API documentation, so raise cost when you make that request. Start from the [Bandsintown API installation support page](https://www.artists.bandsintown.com/support/api-installation). ### Is there a Bandsintown MCP server? You do not need an MCP server to give your agent the Bandsintown API. Jentic connects it directly from the API Directory: import the API, store your app_id once, and your agent calls GET /artists/{artistname} and GET /artists/{artistname}/events on demand. Nothing extra loads into the agent's context, your own Jentic One instance supplies the app_id at call time, and your rules decide which of the two operations the agent may reach. ### Can I limit what my agent is allowed to do with the Bandsintown API? Yes. Because you run Jentic One yourself, your own rules decide which Bandsintown operations the agent may call and which credentials it may use. Since the artist name sits in the URL path for both GET /artists/{artistname} and GET /artists/{artistname}/events, you can pin the agent to a single artist so it only reads that artist's profile and event list. The API is read-only, so there are no write or delete operations for the agent to reach, and the app_id it uses is supplied at execution rather than exposed to the agent.