VenueGo Protect Events

Sign in Get started

Protect Events

Free trial Pre-vetted before they arrive. 25 checks to give the system a try. No card to start. Request a trial

Licensing and data

Data in the UK Stored in London. Deleted after 30 days. ID images are removed after 30 days unless they are still in your review pipeline. Read about compliance

Guides

API reference Sessions, webhooks and the result payload.
Cheap ID verification in the UK What cheap ID verification in the UK should cost for an event, what a low price leaves out, and how Protect Events prices passport and licence checks.
ID verification as a service What ID verification as a service means for an event or promoter, which parts you should buy, and which parts should stay in your own signup or ticketing system.
API-based ID verification How API-based ID verification works for events. Create a session when someone signs up or buys a ticket, and take the age result by webhook.
Age verification for events in the UK How age verification for UK events works before arrival. Set a minimum age per event, and check a passport or driving licence when the guest signs up or buys a ticket.
In-person identity verification for venues How in-person identity verification works before guests arrive. The person and the document are captured together on their phone when they sign up or buy a ticket.
White-label ID verification How white-label ID verification works for events and promoters. Guests see your name and colours when they sign up or buy. Your team still manages the review pipeline.

Talk to us Planning a big date? Tell us the size of the event and we will price the checks around it. Contact us

API reference

Authentication

Server requests use a bearer token created in the VenueGo portal. The token is shown once.

Send the key on every request:

Authorization: Bearer vm_live_...

Keys look like vm_live_… or vm_test_…. Both call the same production API. The prefix is there so you can tell a key’s purpose in your own systems. VenueGo stores only a hash. If you lose a key, revoke it and create another.

Create and revoke keys under Developers in the portal. Treat the key like a password: keep it on your server, not in a mobile app, a front-end bundle, or a ticket email.

A missing or revoked key

The response is 401 with this body:

{
  "error": {
    "code": "unauthenticated",
    "message": "This API token is invalid or has been revoked."
  }
}

There is no session cookie on /api/v1. Browser logins are a different surface and cannot call these routes.

Where the key is allowed

Your backend, when creating, reading, or cancelling a session.
A secret store or environment variable on that server.

Do not send the key from the guest’s phone. The guest uses the url from the create response, which is already scoped to that one session.