Read API

Every request needs a Bearer token in the Authorization header. Keys are scoped to your account's data — you'll only see events you own, applications on those events, and vendor data publicly available via VMScore.

curl https://www.venumark.com/api/v1/events \
  -H "Authorization: Bearer vm_pk_xxxxxxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Keys are revocable from Settings → API keys. Revoked keys stop working immediately on the next request.

60 requests per minute per key. Exceeding the limit returns HTTP 429 with anerror field naming the limit.

Every endpoint returns the same envelope:

{
  "data": { ... } | [ ... ] | null,
  "meta": { ... } | null,
  "error": { "message": "..." } | null
}

On success error is null. On failure data isnull and error.message describes the issue. HTTP status codes are conventional (200/400/401/404/429/500).

List your events. Optional ?status=Published|Draft|Completed|Cancelled filter.

curl "https://www.venumark.com/api/v1/events?status=Published" \
  -H "Authorization: Bearer $VENUMARK_KEY"

Single event detail. 404 if you don't own it.

curl https://www.venumark.com/api/v1/events/00000000-0000-0000-0000-000000000000 \
  -H "Authorization: Bearer $VENUMARK_KEY"

List applications across all your events. Optional ?event_id=<uuid>to scope to one event. Includes the vendor's VMScore (when available), recorded outcome (post-event), deposit status, and any custom-question responses.

curl "https://www.venumark.com/api/v1/applications?event_id=$EVENT_ID" \
  -H "Authorization: Bearer $VENUMARK_KEY"

Vendor lookup by license number. Returns VMScore, risk tier, recommendation, violations history, and platform reliability when the vendor has applied to events on VenuMark. Useful for pre-screening before sending an invite. Required: ?license_number=<MFDV-...>.

curl "https://www.venumark.com/api/v1/vendors?license_number=MFDV-7742" \
  -H "Authorization: Bearer $VENUMARK_KEY"

The /v1/ path is stable — additive changes (new fields, new endpoints) ship without a version bump. Breaking changes get a new version path. We'll email Pro accounts at least 90 days before any v1 deprecation.