API Documentation

The DYVE REST API lets you access event, artist, and venue data for your own applications and integrations.

Overview

The DYVE API is a RESTful JSON API. All responses are returned in JSON format. The API uses standard HTTP status codes and supports CORS for browser-based access.

Authentication

API requests require an API key passed via the x-api-key header.

curl -H "x-api-key: YOUR_API_KEY" \
     https://api.dyve.app/api/v1/share/metadata/event/fabric-london

Base URLs

Environment	Base URL
Production	`https://api.dyve.app`
Development	`https://api.dyve.dev`
Staging	`https://api-staging.dyve.dev`

Rate Limits

API requests are rate limited to prevent abuse:

Read (GET): 240 requests/minute
Write (POST/PUT/DELETE): 240 requests/minute per user
Auth endpoints: 20 requests/minute per IP

When rate limited, the API returns 429 Too Many Requests.

Retrieve Open Graph metadata for any DYVE entity. Used by the dyve.to short link server for social preview cards.

GET /api/v1/share/metadata/:type/:id

Parameters:

type — Entity type: event, artist, user, venue, label, organizer, circle
id — Entity UUID or slug

Response:

{
  "title": "Amelie Lens | Artist on DYVE",
  "description": "Listen to Amelie Lens and track their upcoming events on DYVE.",
  "image_url": "https://img.dyve.app/images/artists/amelie-lens.jpg"
}

The dyve.to domain serves SSR pages with Open Graph meta tags for rich social previews.

Entity	URL Pattern	Example
Event	`/event/:slug`	`dyve.to/event/fabric-anniversary`
Artist	`/artist/:slug`	`dyve.to/artist/amelie-lens`
Venue	`/venue/:slug`	`dyve.to/venue/berghain`
User	`/user/:username`	`dyve.to/user/david`
Circle	`/circle/:id`	`dyve.to/circle/abc-123`

Events

GET /api/v1/guest/map/events

Returns events near a geographic coordinate within a date range. Used by the DYVE map view.

Artists

GET /api/v1/guest/artists/:id

Retrieve artist profile, social links, and upcoming events.

Venues

GET /api/v1/guest/manage/venues/:id

Get venue details including location, capacity, and upcoming schedule.

Search

GET /api/v1/guest/search?q=:query

Full-text search across events, artists, venues, and users.

Error Handling

The API uses standard HTTP status codes:

200 OK              — Success
400 Bad Request     — Invalid parameters
401 Unauthorized    — Missing/invalid auth
403 Forbidden       — Insufficient permissions
404 Not Found       — Resource not found
429 Too Many Reqs   — Rate limited
500 Server Error    — Something went wrong

SDKs & Libraries

Official SDKs are coming soon. In the meantime, any HTTP client works. The API returns JSON with standard REST conventions.

For partnership integrations, contact [email protected].

Restricted Access