Mobile API Contract
Eventonomy overviewFree + ProGet Eventonomy →
This page is the plugin side of the contract a companion mobile app consumes. Everything here is a normal part of the eventonomy/v1 REST surface documented in the REST API Reference - there is no separate “app API”, no second namespace, and no app-only authentication scheme. This page collects the routes and fields an app actually needs, in the order an app needs them, and states what the plugin does not own.
The app itself is a separate product and is not shipped with the plugin. Nothing on this page installs, builds, or configures an app - it documents what the site serves.
What You Will Learn
Section titled “What You Will Learn”- How an app authenticates, and why there is no first-party token exchange
- The connect handshake: the public bootstrap block and the per-user identity block
- The event read contract: which viewer-relative fields the list and the detail carry, and which of them are cacheable
- The registration contract that tells an app whether to render a register button at all
- Where the write surface is closed to banned accounts
- What Eventonomy does not own: CORS, transport security, and app packaging
Contract Map
Section titled “Contract Map”Each capability below is one row of the contract. The identifiers are the ones the app-side contract document uses, so the two can be read side by side.
| Id | Capability | Where it lives |
|---|---|---|
| C1a | Public bootstrap (branding, gating, legal, minimum version) | GET /settings/app-config -> the app block |
| C1b | Per-user identity | GET /me |
| C1c | License gate on the app | Pro filters evnm_rest_app_config |
| C2 | Ban gate on writes | rest_pre_dispatch, evnm_user_is_banned |
| C3 | Native push | POST / DELETE /push/devices (Free registers, Pro delivers) |
| C4 | Viewer-relative event state | GET /events?fields=card and GET /events/{id} |
| C5 | Check-in token for free registrations | Minted inline when an RSVP is created |
| C6 | In-app notification feed | /notifications routes |
| C7 | Self-serve account deletion | DELETE /me |
| C8 | Report an event | POST /events/{id}/report |
| C9 | My registrations (upcoming and past) | GET /rsvps/mine |
Authentication
Section titled “Authentication”Auth is WordPress’s own Application Passwords over HTTP Basic, and sign-in is WordPress core only. There is no first-party JWT, no refresh-token flow, no plugin password form and no plugin credential route. The app stores an application password and sends it on every request.
There are two ways the app comes to hold one, and the site’s own config says which applies (see the auth block below):
- The site’s connect bridge, when one is advertised in
auth.connect_url. On a site running BuddyNext alongside Eventonomy, BuddyNext owns site auth and its bridge carries the site’s social providers and two-factor; Eventonomy registerseventonomy://in its allowlist and stands down. One door per site. - WordPress core’s authorize screen (
wp-admin/authorize-application.php), the standalone door, whenauth.connect_urlis empty. The member signs in through the site’s real login (including any second factor), approves the app, and core returns the new credential to theeventonomy://deep link.AppAuthorizeAccesskeeps this screen usable: the app’s deep-link scheme survivesesc_url()there, and a WooCommerce-style wp-admin block is exempted for that one screen so an attendee can reach it.
Register and lost password open wp-login.php in the browser. auth.register mirrors core’s “Anyone can register” (users_can_register), so the app offers “Create account” only when the site allows it.
Reconnecting replaces: when core mints a new application password, older rows with the same app_id for that member are removed, whichever door minted it. Rows without an app_id (created by hand in the profile) are never touched.
POST /auth/app-password(username and password exchange), theapp_password_loginsetting, theevnm_app_password_login_enabledfilter, theevnm_app_credential_issuedaction and thepassword_loginandnoncekeys of the app-config are removed. A client that still calls the route gets404.
curl -u "jane:abcd EFGH ijkl MNOP qrst UVWX" \ https://example.com/wp-json/eventonomy/v1/meTwo consequences an app must plan for:
- HTTPS is mandatory in production. WordPress core disables Application Passwords on a site it does not consider secure, so the credential screen is simply absent over plain HTTP. This is core behaviour, not an Eventonomy setting, and Eventonomy cannot relax it.
- An application password bypasses any plugin-level login gate, because core authenticates it on
rest_authentication_errorsbefore any Eventonomy code runs. That is exactly why the write surface has its own gate - see below.
Cookie plus X-WP-Nonce still works for in-browser clients and is unchanged. Browser clients get their nonce from the Interactivity store, not from the app-config.
The Ban Gate on Writes
Section titled “The Ban Gate on Writes”includes/Providers/BanGateProvider.php hooks rest_pre_dispatch and rejects a banned member on every non-read request whose route starts with /eventonomy/v1. GET, HEAD and OPTIONS stay open, so a banned member can still browse.
add_filter( 'evnm_user_is_banned', function ( bool $banned, int $user_id ): bool { return $banned || my_community_is_suspended( $user_id );}, 10, 2 );Out of the box the signal reads a truthy evnm_banned user meta, which an administrator sets from the user profile screen. Guest writes (guest RSVP, guest order, magic-link requests) run as user 0 and are not covered by this gate - they are covered by the spam guard and rate limiter instead.
A blocked request returns 403 evnm_forbidden.
Connect Handshake
Section titled “Connect Handshake”1. Public bootstrap - GET /settings/app-config
Section titled “1. Public bootstrap - GET /settings/app-config”The whole payload is site-level and cacheable. The app-specific part is the app key, built by SettingsController::app_bootstrap():
{ "app": { "app_enabled": true, "min_app_version": "1.0.0", "branding": { "app_name": "Riverside Events", "logo_url": "https://example.com/wp-content/uploads/site-icon.png", "login_bg_url": "", "accent_color": "#4d7c0f" }, "legal": { "privacy_url": "", "terms_url": "" }, "push": { "enabled": true } }, "auth": { "social_providers": [], "twofactor": false, "register": true, "app_passwords_available": true, "connect_url": "https://example.com/login/connect-app/", "connect_schemes": ["eventonomy"] }, "site_rules": { "...": "see Site rules below" }}The auth block is a shared Wbcom shape, published in the same form by every Wbcom product, so one reader in the app serves all of them. It tells the app which door to use on THIS site. The payload carries no nonce and no password_login key, and it is identical for a guest and a signed-in member.
| Key | Source | Notes |
|---|---|---|
app_enabled |
Pro active and the app_enabled setting |
Pro then ANDs a valid license on top. Fail-closed. |
min_app_version |
app_min_version setting |
Defaults to 1.0.0. The app decides what to do with a build below it. |
branding.app_name |
app_name setting, else the site title |
Never empty. |
branding.logo_url |
app_logo setting, else the WordPress site icon |
Empty when neither is set. |
branding.login_bg_url |
app_login_bg setting |
Empty by default. |
branding.accent_color |
app_accent setting, else #4d7c0f |
Never empty. |
legal.privacy_url |
get_privacy_policy_url() |
Empty unless the WordPress privacy page is published. |
legal.terms_url |
app_terms_url setting |
Empty by default. |
push.enabled |
app_push_enabled setting |
Whether the app should register the device at all. |
auth.connect_url |
The site’s connect bridge | BuddyNext’s bridge when BuddyNext is active; empty otherwise - Eventonomy ships no bridge of its own, so an empty string means “open core’s wp-admin/authorize-application.php”. Never guess this path. |
auth.connect_schemes |
evnm_app_connect_schemes |
Deep-link schemes this site may hand a credential to. eventonomy is ours; siblings join through the filter. |
auth.app_passwords_available |
wp_is_application_passwords_available() |
False on an insecure site, where no door can work. |
auth.register |
users_can_register |
Whether to offer “Create account” (opens wp-login.php registration in the browser, so the owner’s signup flow stays intact). Lost password also opens wp-login.php. |
auth.social_providers / auth.twofactor |
Always [] / false here |
Eventonomy has no social login of its own; core’s authorize screen runs the site’s real login, including any second factor. On a combined site the bridge carries both behind BuddyNext’s login page. |
site_rules |
Site settings | The rules the app mirrors so it behaves like the website. See Site rules. |
Both legal URLs are empty on a fresh install, and the privacy one stays empty even on a site that has a privacy page, because WordPress creates that page as a draft and get_privacy_policy_url() returns nothing for an unpublished page. An app must treat both as optional strings and hide the link rather than render a dead one. The owner-facing fix is documented in Mobile App.
app_enabled is a two-key gate, and Free provides only the first key:
// Free: provisional.'app_enabled' => defined( 'EVENTONOMY_PRO_VERSION' ) && (bool) Settings::get( 'app_enabled', true ),
// Pro, on evnm_rest_app_config (priority 20): AND a valid license.$config['app']['app_enabled'] = ! empty( $config['app']['app_enabled'] ) && License::is_valid();So a Free-only site always reports app_enabled: false and the app cannot be enabled there at all, and a Pro site whose license lapses starts reporting false at the next connect.
Extend the payload with evnm_rest_app_config. Anything you add here is public and cacheable - never put per-user data on this route.
Site rules
Section titled “Site rules”site_rules (built by SettingsController::site_rules()) carries the site settings the app mirrors, resolved the way the website reads them. It is site-level, so it stays on the public cacheable route.
| Block | Key | Meaning |
|---|---|---|
registration |
account_policy |
The site’s account policy for registering (evnm_account_policy()). |
allow_rsvp_guests |
Whether a guest may bring extra guests. | |
rsvp_max_guests |
Cap per RSVP; 0 means no cap. |
|
rsvp_deadline_hours |
Hours before start when registration closes; 0 means open until start. |
|
display |
timezone_display |
event by default; the owner can choose another display mode. |
date_format, time_format |
PHP date() patterns; fall back to WordPress’s own formats when the plugin setting is empty. |
|
week_starts_on |
0 is Sunday. |
|
single_event |
single_show_map, single_show_organizer |
Whether the event page shows the map and the organizer. |
show_add_to_calendar |
The setting AND the ics feature being on. |
|
donations |
donations_enabled |
Whether donation tickets are offered. |
donation_suggested |
Suggested amounts as numbers (whole amounts are ints), parsed from the comma list setting. | |
versions |
free, pro |
Plugin versions; pro is null when Pro is not active. |
Pro adds no keys to site_rules. The app hands paid checkout to the website, so checkout rules such as payment methods and coupons are not part of the app config.
2. Per-user identity - GET /me
Section titled “2. Per-user identity - GET /me”Auth-only, and always sent with Cache-Control: no-store, private so a shared cache can never hand one member’s identity to another. Returns id, display_name, username, email, avatar_url, roles, can_create_events (kept top-level for older app builds), and a capabilities object. Extend it with evnm_rest_me.
capabilities key |
Meaning |
|---|---|
can_create_events |
The resolved create gate, so the app never offers a create action the API will refuse. |
can_manage_others_events |
The member may edit any event (evnm_edit_others_events). |
can_manage_settings |
The member may change plugin settings (evnm_manage_settings). |
Per-event rights ride on each event - see can_edit, can_manage_rsvps and can_checkin below.
The Event Read Contract
Section titled “The Event Read Contract”Two shapes, one preparer. GET /events?fields=card returns the lean card payload; GET /events/{id} returns the detail payload. Both carry the viewer-relative fields below.
On the card list - GET /events?fields=card
Section titled “On the card list - GET /events?fields=card”| Field | Type | Meaning |
|---|---|---|
viewer_rsvp |
string or null | The signed-in member’s own RSVP status on this event, or null. |
viewer_rsvp_id |
int or null | The id of that RSVP, so the app can PATCH or DELETE it without a lookup. |
has_checked_in |
bool | Whether the member has already been checked in. |
capacity_remaining |
int or null | Places left. null when capacity is unlimited (0) or when the owner has the “show remaining” setting off. Read is_full for the state either way. |
can_edit |
bool | The viewer may PATCH this event. |
can_manage_rsvps |
bool | The viewer may read the attendee roster and manage RSVPs. |
can_checkin |
bool | The viewer may check people in: can_manage_rsvps AND Pro active (check-in is Pro’s POST /checkin). |
can_duplicate |
bool | The viewer may use POST /events/{id}/duplicate: they can edit the event and create events. |
can_delete |
bool | The viewer may DELETE /events/{id}. |
can_refund_all |
bool | The viewer manages the event’s orders and a payment gateway that can refund is active, so POST /events/{id}/refund-all is offered. Cancelling an event is PATCH status, so it is can_edit. |
ics_url |
string | Detail only. The event’s calendar file link, built like the web page’s, so a link-only event carries its key. Empty when the page offers no calendar file (a cancelled event, no upcoming date, or the calendar feature or setting off). Never in lists. |
remaining_label |
string | The spots-left sentence the web card prints (“3 spots left”, “This event is full. Join the waitlist.”), from evnm_remaining_label(). Empty when there is nothing to say. Show it verbatim. |
The viewer_* and has_checked_in fields are resolved in one batched call for the whole page (RsvpRepository::viewer_status_for_events()), never per row. The six can_* fields are capability math on the row already loaded, so they add no query. They are always present, false for guests, so a guest and a member payload share one shape. capacity_remaining is not per-user - it is the event’s headcount against its capacity - so it is attached for guests too.
Manageable list. GET /events?manageable=1 returns the events the viewer may manage, in every status, for an app “My events” screen. A member with evnm_edit_others_events gets every event; anyone else gets their own. Past events are included. A guest gets an empty page. Pass status to narrow it.
Caching is split deliberately. The per-user fields are emitted as null / false rather than omitted, so the response shape is identical for a guest and a member. A guest card page carries no per-user data and stays cacheable; once the request is authenticated the response is sent with Cache-Control: no-store, private.
GET /wp-json/eventonomy/v1/events?fields=card&per_page=20fields=card is response-shaping, not a filter. It also attaches the display-ready card fields (date, month, day, going, going_label, category, price_label, hue, tags) through batched queries, so an appended page never triggers an N+1.
On the detail - GET /events/{id}
Section titled “On the detail - GET /events/{id}”Everything from the card contract, plus:
| Field | Type | Meaning |
|---|---|---|
going |
int | Confirmed headcount. |
going_label |
string | The same count pre-formatted server-side (“12 going”), correctly pluralized and translated. Empty string when nobody is going. |
attendees_preview |
array | Up to 5 entries of { user_id, display_name }. With Pro active each entry also carries avatar_url (absolute, from evnm_avatar_url(); '' for a guest). |
viewer_order_id |
int or null | When the signed-in member’s place on this event is a ticket, the order it belongs to; null otherwise. The web hides Cancel for a ticketed place (a refund goes through the order), so the app should too. |
registration |
object | The registration contract - see below. |
price_free |
bool | true when the event has no paid ticket. The same value the card list carries. |
price_label |
string | The price summary the web page prints (“Free”, or “From” and the lowest price), formatted server-side by evnm_event_price_label(). |
takes_guests |
bool | Whether this event lets a registrant bring extra guests (evnm_event_takes_guests()). Show a guests control only when this and site_rules.registration.allow_rsvp_guests are both true, capped at rsvp_max_guests. |
recurrence.summary |
string | The translated repeat sentence the web prints (“Repeats weekly”), from evnm_recurrence_summary(), beside recurrence.freq and recurrence.interval. Empty for a one-off event. RSVPs and capacity apply to the whole series, so do not send an occurrence_id with an RSVP. |
attendees_preview carries user_id and display_name only, and never an email address. It is the avatar stack a visitor already sees on the public event page; the full attendee roster stays behind GET /events/{id}/attendees, which is manager-only. Guests who registered without an account are counted in going but are never listed.
going_label is formatted on the server on purpose: the app renders it verbatim and does not need its own plural rules or translation catalogue for the count.
The registration contract
Section titled “The registration contract”{ "registration": { "mode": "external", "questions": [ { "id": "dietary", "label": "Dietary needs", "type": "select", "required": false, "options": [ "None", "Vegetarian", "Vegan" ] } ], "external_url": "https://example.org/tickets/summer-social" }}modeis one ofrsvp(people register here),external(registration lives on another site), ornone(no registration needed). An unknown stored value resolves torsvp. Read this before rendering anything: an app that always shows a register button will offer registration on an event that refuses it.questionsare resolved definitions, not raw ids. The question bank is a site-wide setting and an event stores only a selection, so returning ids alone would force every client to fetch and join the bank itself. Each entry isid,label,type,required,options. Only the fields an attendee is asked to fill are exposed - never the whole event settings blob.external_urlis present only whenmodeisexternal. It is omitted otherwise, so a stale URL left over from a mode change can never be mistaken for an active external flow.
The registration block is attached for both the card and the detail shape, so a list screen can already tell which cards should show a register affordance.
Virtual events
Section titled “Virtual events”virtual.join_url and virtual.instructions are emitted as empty strings to anyone who is not a registered attendee of that event. Do not cache an authenticated event detail response into a shared store.
virtual.join_live (bool) is the web page’s “Join event” moment, computed by Eventonomy\Support\JoinWindow. It is true only when the viewer holds a join link and now falls between the lead time before the start and the end of the event. The lead defaults to one hour and is filterable:
add_filter( 'evnm_join_button_lead_seconds', function ( int $seconds, int $event_id ): int { return 15 * MINUTE_IN_SECONDS;}, 10, 2 );The card shape carries no start or end, so join_live is false there. Read the detail.
The Rest of the App Surface
Section titled “The Rest of the App Surface”These routes are documented in full in the REST API Reference; this is the app-relevant summary.
| Need | Route | Notes |
|---|---|---|
| My registrations | GET /rsvps/mine?status=going|past |
Always self-scoped; there is no user parameter. Rows add when_label, event_url and checkin. See below. |
| My orders | GET /orders, GET /orders/{id} |
Self-scoped for members. Every row carries event_title, when_label (the site’s formatted date, or “Date to be announced”) and event_url. The owner’s rows add attendees[].checkin. See below. |
| Pay and return | POST /orders with return_url |
Hands the buyer back to the app after the gateway. See below. |
| Email switches | GET / PATCH /me/notification-preferences |
Self-scoped, no-store, private. See below. |
| My organizer numbers | GET /me/stats |
Signed in, always scoped to the caller’s own events, no-store, private. Takes range (7, 30, 90 or custom with from / to, site-timezone Y-m-d), plus orderby, order, page, per_page (max 100) for the per-event list. Returns window, overview, period and events (a list envelope), the same numbers the dashboard and Reports page show. |
| Attendee CSV | GET /events/{id}/attendees/export |
Event managers only (can_manage_rsvps). Streams text/csv, not JSON; open it as a download. |
| Check in (Pro) | POST /checkin |
Organizer or administrator scan. Send token and event_id. See below. |
| Notification feed | GET /notifications, GET /notifications/unread-count, POST /notifications/{id}/read, POST /notifications/read-all |
Auth-only, self-scoped, no-store, private. |
| Push registration | POST /push/devices, DELETE /push/devices |
Tokens live in the evnm_push_tokens user meta. Re-posting a token refreshes it; the same token registered by another member moves to the new one; a member keeps their ten most recent devices; a token that is not an Expo token returns 422; DELETE is idempotent. Registration is Free; delivery is Pro. |
| Report an event | POST /events/{id}/report |
Logged-in only, 5 per hour. Store-compliance requirement. |
| Delete my account | DELETE /me |
Requires an exact confirm_username; administrators are refused. Deletion is permanent: event data is anonymised, events they organised stay, and posts and pages they wrote on the site are deleted with the account. GET /me returns delete_account_notice, the text to show before asking for the username (it names the number of posts and pages when there are any); a wrong username answers 422 with the same text. |
My registrations and tickets
Section titled “My registrations and tickets”GET /rsvps/mine rows carry the display fields the web dashboard prints, from the same formatters:
| Field | Type | Meaning |
|---|---|---|
when_label |
string | The event date and time, formatted server-side. “Date to be announced” when the event has no date. |
event_url |
string | The event permalink (filter evnm_event_permalink). |
checkin |
object or null | { token, url } for the member’s own ticket, or null when the ticket has no code. |
event_status |
string | The event’s own status (published, cancelled, …). A cancelled event’s rows still read going, so show the cancelled state from this field. |
order_id |
int or null | The order a ticketed place belongs to. |
The response is sent with Cache-Control: no-store, private, because rows carry a check-in code. checkin is null on past rows.
GET /orders and GET /orders/{id} add the same checkin object to each attendees[] entry, for the order’s owner only and only on a paid order. A ticket has a code (evnm_ticket_has_code()) when an extension that draws codes is active (Pro), the seat is still going (a cancelled or refunded seat has none), it has a token, and the event is not cancelled and has a door. The url is what the QR encodes.
Each attendees[] entry on GET /orders and GET /orders/{id} also carries label, the ticket-holder line the web confirmation and order page print, from the same helper (evnm_order_ticket_labels()). The holder’s own seat reads their name, a later seat that carries the holder’s name reads “Guest of name is unchanged and is still the stored name. Show label; use name only where the real stored name matters.
These are the only REST outputs that carry a check-in token. Rosters, other members and guests stay token-free.
Three shared helpers in includes/functions.php hold the rule, so the web ticket, the email QR and the app all agree:
| Helper | Returns |
|---|---|
evnm_ticket_has_code( $rsvp, $event = [] ) |
bool - whether the ticket has a code right now. |
evnm_checkin_url( $token ) |
The URL a ticket QR encodes (?evnm_checkin=<token> on the home URL), '' for an empty token. Filter evnm_checkin_url. Pro’s QrService::checkin_url() calls it. |
evnm_ticket_checkin( $rsvp, $event = [] ) |
{ token, url } or null. Send it only to the ticket’s owner. |
Returning to the app after payment
Section titled “Returning to the app after payment”POST /orders accepts an optional return_url, an app deep link such as eventonomy://orders. OrderService::app_return_url() validates it and the order stores it. After the gateway finishes, Pro’s payment return handler (and the WooCommerce thank-you redirect) sends the buyer to return_url?order_id=<id>&status=<status>, where status is the order’s current status.
- The scheme must be listed on the filter
evnm_order_return_url_schemes. It is empty by default and fails closed. The mobile-app area (AppConnect) adds the app-connect schemes, soeventonomyworks out of the box. - Web schemes (
http,https) and script schemes are refused even if a filter lists them. So are values with whitespace or control characters and values over 2000 characters. - A rejected value returns
400 evnm_invalid_return_url. - The link is a hint, never an authorization. The app re-reads
GET /orders/{id}for the truth.
Email switches
Section titled “Email switches”GET /me/notification-preferences returns { items }, one row per suppressible email type: { key, label, description, enabled, locked }. PATCH takes either { "key": "event_reminder", "enabled": false } or { "preferences": { "event_reminder": false } } and returns the updated list. Both are self-scoped and sent no-store, private; guests get 401.
The switches write the same suppression row the emailed unsubscribe link uses (UnsubscribeService), so the link, the web dashboard (My Events, Profile) and the app agree. UnsubscribeProvider enforces the per-type opt-out: is_suppressed( $email, $email_key ) runs on every recipient before a message is sent.
| Status and code | When |
|---|---|
422 invalid_preferences |
The body names no key. |
422 unknown_preference |
The key is not a suppressible email type. |
422 preference_locked |
The key is the locked one (confirmations and receipts are always sent). |
500 preferences_not_saved |
The row could not be written. |
Push payload
Section titled “Push payload”Free stores device tokens; Pro’s ExpoPushChannel sends. Every push has data with exactly these keys, so the app can route on them:
| Key | Meaning |
|---|---|
object_type |
What to open: event, or '' when there is no target (open the inbox). |
id |
That object’s id, 0 when there is none. |
type |
The message kind (the email key, such as event_reminder), for copy and analytics. Route on object_type and id. |
There is no notification_id: the in-app feed row is written by another channel. To mark the tapped message read, the app reads the first page of GET /notifications, takes the newest unread row with the same type, object_type and object_id, and calls POST /notifications/{id}/read. When the owner turns off app_push_enabled (Settings > Mobile app, the push.enabled flag above), no device is contacted whatever is registered.
Check-in errors (Pro)
Section titled “Check-in errors (Pro)”POST /checkin takes a token and an event_id, and both are required: without event_id (or with 0) it returns 400. For a recurring event send occurrence_id too (the date being admitted); leave it out and the server uses the date happening now. The same ticket admits once per date, so a second scan for the same date answers already while the next date is a new admission. GET /events/{id}/attendees and GET /checkin/stats take the same occurrence_id, and checked_in on the roster then means “checked in for that date”. The door is scoped to that event, and a ticket for another event is refused. There is no fallback that finds the event from the token.
The ticket QR does not hold the bare token. It holds the check-in URL (<home>/?evnm_checkin=<token>, built by evnm_checkin_url()). Read the evnm_checkin query value from the scanned URL and send only that as token. Sending the whole URL matches no ticket.
The caller must be the event’s organizer (its author) or a user with manage_options; an Editor who did not create the event is refused.
| Status and code | When |
|---|---|
401 |
The request is not authenticated. |
403 evnm_pro_forbidden |
The caller may not check attendees in for this event, or no event could be resolved (no event_id and an unknown token). |
404 evnm_pro_invalid_ticket |
The token is empty or matches no ticket. |
409 evnm_pro_wrong_event |
The ticket belongs to a different event than event_id. Nobody is checked in. |
409 evnm_pro_ticket_void |
The ticket was cancelled or refunded. |
409 evnm_rsvp_not_going |
The registration is not Going (No, Maybe, Waitlist). The same code the roster’s manual check-in returns. |
What Eventonomy Does Not Own
Section titled “What Eventonomy Does Not Own”The plugin ships no CORS handling. There is no Access-Control-Allow-* header emitted anywhere, and nothing hooks rest_pre_serve_request or send_headers to add one. Requests to the REST API are served with whatever headers WordPress core and the web server produce.
What that means in practice:
- A native app build is unaffected. Native HTTP clients on iOS and Android are not browsers and do not perform a CORS preflight, so nothing needs allowlisting.
- A browser-hosted build does need allowlisting - a web build, a development tunnel, or anything running the app inside a browser origin that differs from the site’s origin. That is a server or site-level concern: configure it in the web server, a reverse proxy, or a small site snippet on
rest_pre_serve_request. It is deliberately not an Eventonomy setting, because a plugin that guesses an origin allowlist is a plugin that eventually opens one it should not have.
Do not look for a CORS option in the plugin settings; there is none, and adding one is not on the contract.
Transport security
Section titled “Transport security”HTTPS is a hosting concern. Eventonomy does not enforce it, but Application Passwords will not be offered by WordPress on an insecure site, so an app cannot practically authenticate against one.
App packaging
Section titled “App packaging”Store builds, native push credentials, deep links, and the app’s own error copy live in the app project, not here. Nothing in this repository configures them.
What’s Next?
Section titled “What’s Next?”Read the full endpoint listing, including every parameter and error code.
Order links
Section titled “Order links”GET /orders rows for the buyer’s own orders carry receipt_url (token-scoped, opens without a cookie) and invoice_url (paid or refunded orders only). Both are empty strings for anyone else, a manager included. Open them in the in-app browser; the access token itself is never returned.

