Exceptions

Every client-facing exception extends the abstract Exceptions\EventsException (a RuntimeException). errorCode() is the stable code, status() the HTTP status the API answers with, and getMessage() is already the client-safe text — translated into the current locale (events::messages, en and sk), never naming a class, key or table. In your own controllers:

use RoundlyConsulting\Events\Exceptions\EventsException;

try {
    $rsvp = Events::for($event)->rsvp($request->user())->by($request->user())->going(tier: $request->input('tier'));
} catch (EventsException $e) {
    return response()->json(['message' => $e->getMessage(), 'code' => $e->errorCode()], $e->status());
}

EventTransitionDeniedException also has denials() (lifecycle’s denial codes plus no_attendees and rescheduled_through_events), retryAfterSeconds() (0 unless rate limited; the API sends Retry-After) and previousDenial(). CheckInRefusedException::reason() is one of the constants WRONG_EVENT, NOT_GOING, EVENT_NOT_ACTIVE and OUTSIDE_WINDOW.

Errors the API maps from elsewhere

In PHP these pass through unchanged.

Configuration errors

These are the host’s to fix: English, naming the key, and extending the toolkit’s PackageToolkitException. InvalidEventsConfigurationException covers a bad duration, timezone, table name, time of day, URL template or choice — outOfRange() for a value outside its bounds, tooMany() for more than five reminder offsets and keyTypeMismatch() when a model’s key does not fit events.key_type, raised before any SQL. InvalidEventLifecycleException covers an events.lifecycle value that is not a LifecycleDefinition implementing Contracts\EventLifecycle, or one that breaks the contract. The toolkit’s own InvalidConfigurationException covers a model, resource, notification class or list that is not what its key needs.