Search by

omniticket / weezevent

GlitchArt

Omniticket's Weezevent, under any PHP host: an organizer's events with their rates (categories flattened), sessions and sales period, the participants of an event (incrementally), and a ticket's barcode checked at the door - read only, through Weezevent's API (api.weezevent.com).

v1.0.1 2026-11-13 15:07 UTC

This package is auto-updated.

Last update: 2026-11-14 02:14:19 UTC


README

omnisense/omniticket's Weezevent, under any PHP host: an organizer's events with their rates (categories flattened), sessions and sales period, the participants of an event (incrementally), and a ticket's barcode checked among them. Reading only.

Install and a first call

composer require omniticket/weezevent

No account for this first call: Weezevent's answer is recorded (Omniticket\Testing\RecordedHttpClient answers in place of the API), so nothing leaves the process. A real call needs a partner API key (Weezevent gives them to registered partners only) and the organizer's token (or login).

<?php

require __DIR__.'/vendor/autoload.php';

use Omniticket\Testing\RecordedHttpClient;
use Omniticket\Weezevent\WeezeventFactory;

// Weezevent's answer, recorded: nothing sent. HttpClient::create() (symfony/http-client) for a real call.
$http = RecordedHttpClient::routes([
    'GET /events' => '{"events": [{"id": 13824, "name": "Festival d\'été", "date": {"start": "2036-07-10 18:00:00", "end": "2036-07-12 23:00:00"}, "participants": 120, "multiple_dates": 0, "sales_status": {"id_status": 1, "libelle_status": "Vente en cours"}}]}',
]);
$weezevent = (new WeezeventFactory($http))->create(['api_key' => 'recorded', 'access_token' => 'recorded']);

foreach ($weezevent->events() as $event) {
    echo $event->title, ' ', $event->start?->format('d/m/Y H:i'), ' ', $event->availability->sold, " sold\n";   // Festival d'été 10/07/2036 18:00 120 sold
}

With your key, through the family's registry:

use Omniticket\Registry;
use Omniticket\Weezevent\WeezeventFactory;
use Symfony\Component\HttpClient\HttpClient;

$registry = new Registry([new WeezeventFactory(HttpClient::create())], [
    'festival' => ['factory' => 'weezevent', 'options' => ['api_key' => '...', 'access_token' => '...']],
]);

Options: api_key (Weezevent gives API keys to registered partners), access_token (persistent: obtained once) or username and password (exchanged for a token at the first call), timezone (Europe/Paris), currency (EUR), url.

The API, as read on 2026-10-24

Weezevent's API (https://api.weezevent.com): POST /auth/access_token, then api_key and access_token on GET /events, /event/{id}/details, /tickets (rates, nested in categories), /dates (sessions) and /participant/list (last_update for what changed since, include_deleted, include_unpaid; control_status.status 1 is scanned). GET /event/categories needs no key. There is no lookup by barcode: check() reads the event's participants and looks the code up among them.

Terms: access is limited to registered partners; fair use - store what is read locally, filter queries; an abusive key may be restricted. What this package does: event() makes three calls, attendees() two (the participants and the rates' names, kept for the provider's life), check() the same two - an application checking many tickets keeps the list itself (attendees() with updatedSince, then Check::among()). Not verified: whether a very large participant list is cut without paging (max and page are documented without their base).

No PHP client of Weezevent's API was found to reuse.

Usage policy

Declared as data in policy.json (omnisense/contracts' schema), read on 2026-11-10 at the fair use page: 600 requests a minute (per IP), 10 credentials attempts a minute (the access token asked with a login, the operation token); 5 invalid logins ban for 30 minutes (the notes). Storage allowed (Weezevent asks to store what is read and filter by last_update); commercial use, caching, redistribution and attribution unknown. Through omniticket's registry every call is checked against it, a 429 and its Retry-After hold the next calls, and a site may tighten it, never loosen it.

Verified, and not

  • Verified (the core's harness, PHP 8.4): events and their sales status, one event whole (rates across categories, quota 0 read as no quota, sessions, price range), participants with last_update in Weezevent's zone, checks valid, refunded, scanned and unknown, the token from the login, a refused key - against the example responses of Weezevent's documentation, as published (non-breaking spaces of the page turned back into spaces); every class loading with the package's requirements alone (BareTest).
  • Verified live (docker compose run --rm omniticket live, 2026-10-24): GET /event/categories, no key - the host and the JSON as read.
  • Not verified live: everything that needs a partner key.

Licence

MIT. An unofficial client, affiliated with Weezevent in no way.