Attribution & Linking
Concert listings change all the time. A visible source tells fans where the information came from, and a working link sends them to the most current version of each show.
The rule has two parts, and it is the same on every self-serve plan.
- Source credit: a visible "Powered by JamBase" or "Concert data by JamBase" credit, linked to jambase.com.
- Link-through: each event you list links to its ticket link exactly as the API returns it, or to its JamBase event page.
Source Credit
Show a visible credit wherever people see JamBase data in your product.
| Requirement | Details |
|---|---|
| Wording | "Powered by JamBase" or "Concert data by JamBase". Either one is fine. |
| Form | Plain text, or an official mark from the logo pack below. A "Powered by JamBase" lockup counts on its own. Any other JamBase mark counts when it sits next to the text "Powered by JamBase" or "Concert data by JamBase". |
| Link | The credit links to https://www.jambase.com with rel="nofollow". |
| Placement | Visible and readable, near the JamBase data or in the footer of each page or screen that shows it. One credit per screen is enough; you don't need one on every tile. |
| Logo spacing | When using a logo, keep at least 20px of clear space on all sides. |
Text credit example
<footer>Concert data by <a href="https://www.jambase.com" rel="nofollow">JamBase</a></footer>Pick the mark that fits your UI. Don't recolor or distort it, and follow the spacing and rel="nofollow" rules above.
"Powered by JamBase" lockups
Use on light surfaces
Use on light surfaces for extra brand color
Use on dark surfaces
Plain JamBase wordmarks
Use these and the marks below next to the text "Powered by JamBase" or "Concert data by JamBase".
Full-color mark for light surfaces
Use on dark surfaces
"Go See Live Music" lockups
Use on light surfaces
Use on dark surfaces
Square & inline marks
Great for tight or square spaces
Best for inline / favicon-sized attribution
One ZIP with every mark above as a PNG, plus a short README covering usage and spacing rules. These are the official PNGs from the JamBase brand kit.
SVG versions aren't included yet.
Download Logo PackLink-Through
When you list JamBase events, each event links to its ticket link or its JamBase event page.
| Requirement | Details |
|---|---|
| Primary ticket link | Link to the primary ticket link URL exactly as the API returns it |
| Fallback | Events without a ticket link link to their event page on JamBase.com |
| URL modification | Don't modify, shorten or rewrite ticket link URLs, or route them through your own redirect or affiliate tag |
| Summaries | A chart, count or map summary that shows no individual events needs the source credit only |
| Link attribute | All ticket and event links must include rel="nofollow" |
| Link Type | Example |
|---|---|
| Ticket Link | https://ticketmaster.evyy.net/c/... |
| Event URL | https://www.jambase.com/show/artist-venue-20260315 |
Where It Applies
One rule on every self-serve plan, with a few clear exceptions.
| Plans | Attribution |
|---|---|
| MCP, Trial, Developer, Startup, Pro and Pro+ | Source credit and link-through are required. |
| Enterprise | Negotiated in your Order Form, white-label available. Standard terms apply unless your Order Form or SOW says otherwise. |
| Case | What applies |
|---|---|
| Internal-only use | No credit is needed when nothing is shown to end users, for example internal analytics, reporting or staff-only tools. The rule applies as soon as the data, or something built from it, reaches end users. |
| White-label | Only a signed Order Form or SOW can waive the source credit. It can also change the link-through. Talk to us about Enterprise. |
| Existing subscriptions | A subscription active before October 20, 2026 keeps the attribution terms it had while it stays on the same plan and billing cadence. Renewals and card updates don't change that. A new subscription, a plan or billing-cadence change, or a new Order Form moves it to the current rule. |
Compliance
We check implementations and help fix gaps.
Attribution is part of your agreement
Next Steps
- Getting Started: make your first API call
- Using Images (who owns the images the API returns and how to display and cache them)
- Pricing: compare plans, including Enterprise white-label options