Support

What helps us answer quickly

For anything that looks like a bug, include:

• The full request — method, path and query string. Never the key itself; the first eight characters are enough to identify it.
• What you got back, including the error.type and the HTTP status.
• Roughly when it happened, with a timezone.

If a response looks wrong rather than broken — a missing lineup, a venue in the wrong city, a duplicated artist — send the url from the payload. That points at the record on edmdb.net and is the fastest way for us to see what you are seeing.

Licensing and commercial use

Questions about what you may build, redistribute or resell go to the same address. See pricing for the outline first — but if your case is not obviously covered there, ask rather than guess.

Keys and billing

Creating, revoking and inspecting keys is self-service at edmdb.net/account/developer, and plans are managed at edmdb.net/account/billing. We cannot recover a lost key — they are stored hashed — so the fix is always to revoke and create another.