canonical: https://jentic.com/apis/songkick.com/songkick-api

# Songkick API

The Songkick API provides easy access to the biggest live music database in the world with over 6 million upcoming and past concerts. Search for events by artist, date, venue, and location, access user's events and trackings, complete concert history for artists (gigography), event details, venue details, similar artists, and more. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get artist's upcoming events, search for events. Covers 2 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Get artist's upcoming events
- Search for events
- Integrate Songkick API into automated workflows
- Query and filter Songkick API records by parameters
- Monitor Songkick API operational status and events

## Use cases

### Analytics Operations

Use the Songkick API to perform analytics operations programmatically. The API provides 2 endpoints covering core functionality including get artist's upcoming events, search for events.

Example prompt: Call GET /artists/{artist_id}/calendar.json to get artist's upcoming events

### Data Retrieval and Monitoring

Query Songkick API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Songkick API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Songkick API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get artist's upcoming events', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /artists/{artist_id}/calendar.json | Get artist's upcoming events |
| GET | /events.json | Search for events |

## Key resources

- **Events** — Event search and calendar operations

## Why Jentic

- **Setup:** Wiring the Songkick API by hand means appending its apikey query parameter on every call, pointing at the api.songkick.com/api/3.0 host, and handling paging and retries yourself. Through Jentic you install once, import the Songkick API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Songkick API puts the artist id in the URL path (/artists/{artist_id}/calendar.json), so a rule can pin your agent to one artist's upcoming calendar. Every endpoint here is read-only, and you choose which operations are in the allowed set, so anything you do not add stays out of reach.
- **Credential handling:** Your Songkick API key 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 an artist's upcoming events' or 'search events', and Jentic returns the matching Songkick API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Songkick API use?

The Songkick API uses an API key passed in the `apikey` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get artist's upcoming events with the Songkick API?

Yes. Use the GET /artists/{artist_id}/calendar.json endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Songkick API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get artist's upcoming events through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get artist's upcoming events'. Jentic returns the matching Songkick API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Songkick API have?

The Songkick API exposes 2 endpoints covering events operations.

### Can I limit what my agent is allowed to do with the Songkick API?

Yes. Because you run Jentic One yourself, your own rules decide which Songkick operations the agent may call, so you can allow just GET /artists/{artist_id}/calendar.json or GET /events.json and leave everything else out of reach. Since the artist id sits in the URL path, a rule can pin the agent to one artist's upcoming calendar rather than the whole catalogue. Both endpoints are read-only, and the stored API key is injected at execution time, so the agent can only fetch the event data you have permitted.