Using Images
The image field
Events, artists, venues, streams and festivals can include an image URL.
The image field is an absolute URL to an illustrative image hosted on www.jambase.com, usually 1480 by 832 pixels.
The API returns the URL exactly as it is stored, without rewriting or resizing.
{"@type": "Concert","identifier": "jambase:12345678","name": "Artist Name at Venue Name","image": "https://www.jambase.com/wp-content/uploads/2024/05/artist-name-1480x832.jpg"}
| Record | What the image usually shows |
|---|---|
| Event, artist, venue and stream | An illustrative image, such as a press photo or logo |
| Festival | A general image or logo for the festival. It is not a lineup poster: JamBase does not store or serve lineup posters. |
Who owns the images
Most images belong to third parties, not to JamBase.
Most images are press photos and logos owned by artists, venues, festivals or photographers.
JamBase does not own them and grants no license to them. All rights stay with the photographer, artist, venue or festival.
Displaying images
Show each image next to the data it belongs to.
| Practice | Details |
|---|---|
| Source | Load the image from the URL in the image field, or from your own cached copy (see caching and refreshing). |
| Keep it with its record | Show the image next to the event, artist, venue, stream or festival it belongs to. |
| Attribution | Follow the attribution rules for your plan wherever the images appear. |
| Sizing | Scale or crop the image to fit your layout. |
| Fallback | Show a placeholder when an image is missing or fails to load. |
A typical web display, with a placeholder if the image fails to load:
<imgsrc={event.image}alt={event.name}loading="lazy"onError={(e) => {e.currentTarget.src = "/placeholder-event.png";}}/>
Caching and refreshing
JamBase is not an image CDN. For production traffic, cache images on your side and keep the cache in step with your data.
| Practice | Details |
|---|---|
| Cache on your side | Serve images from your own server, CDN or image service rather than loading every view from www.jambase.com. |
| Key the cache by URL | A replaced image normally gets a new URL, so the URL tells you when your copy is out of date. |
| Refresh with your sync | When a record's image URL changes, fetch the new image and drop the old copy. When the field is empty or the record is removed, delete the cached copy. |
| Re-check regularly | On a regular schedule, such as weekly, confirm cached images still resolve at their source URL and delete copies that return 404 or 410. |
| Delete when you leave | When your subscription or account ends, delete cached images along with the rest of your synced copy. |
| Fetch gradually | Fetch new images as your sync finds them rather than in one large batch. The media servers use bot protection, so contact support if your server's requests are blocked. |
Reliability
Images are provided as-is.
Images have no SLA and no guarantees about size or format. An image URL can change or be removed at any time.
Plan your layout to work without an image, and show a placeholder when one is missing or fails to load.
If images fail to load for some of your users, see why images might not load.
Removals and rights holders
Stop showing an image, including any cached copy, when it is removed or a rights holder objects.
Removed images must come down
A removed image usually shows up as a changed or empty image field in your next sync, or as a URL that no longer loads.
Rights holders who want an image removed can contact data@jambase.com.
Next Steps
- Attribution & Linking (how to credit JamBase and link to tickets)
- Bulk Ingest & Delta Sync (keeping a local copy current, including images)