The PI Events for SeatGeek Developer licence extends the publishing platform into an integration layer. It includes every Standard and Business feature, then adds a SeatGeek WordPress REST API, authentication, rate limiting, webhooks and customization tools for headless sites, mobile applications and custom themes.
Review the complete SeatGeek WordPress REST API Developer licence.
REST endpoints for connected applications
Developer exposes event collections and individual event records, performer and venue collections, and related upcoming-event routes. An iCal endpoint makes imported events available to calendar-compatible consumers. Responses are cached through the same central Cache Control Center used by the frontend.
This means a project can curate or import event data in WordPress, then deliver it to a JavaScript frontend, mobile app or approved external service without building an unrelated event database.
API-key authentication and rate limiting
Administrators can require an API key and generate a key from the plugin interface. Clients send it as a Bearer token or supported request parameter. Per-client token-bucket rate limiting controls how many requests a consumer may make within a configured window, and responses can include rate-limit headers.
These controls are not a substitute for a complete application security review, but they provide a practical boundary for event-data endpoints intended for known clients.
Cache-aware API delivery
Developer REST responses use centralized cache policies and expose an X-Cache header indicating a hit or miss. Hooks such as pisg_cache_policy and pisg_cache_flushed allow technical teams to alter policy or react when cache groups are cleared. Safe caching, refresh locks and stale fallback continue to protect upstream SeatGeek requests.
Webhooks for import and entity synchronization
A webhook URL can receive notifications when import or entity-sync operations complete. This helps an external search index, deployment process or connected application react to changes without continually polling WordPress. A test control lets the administrator verify the destination during setup.
Theme templates, ACF and multisite
Theme template overrides allow developers to replace plugin presentation files for event cards, event details, performer profiles and venue profiles while preserving the plugin’s data workflows. ACF synchronization can map SeatGeek values into a selected field group for projects built around Advanced Custom Fields.
Multisite-aware functionality supports network contexts while retaining the one-domain licensing rule. Each Standard, Business or Developer purchase covers one server-verified domain; Developer does not mean unlimited client installations.
Plan the API consumer before enabling access
Document which application will call the API, which routes it requires, how often it refreshes and how failures should be handled. A public display application may need event collections and details, while a venue guide may also require venue profiles and upcoming-event relationships. Request only the fields and result sizes the consumer needs.
Store API keys securely in the consuming application and rotate them if exposure is suspected. Avoid placing a privileged key in publicly readable source code. Test unauthorized requests as well as successful ones so the integration fails predictably.
Designing a rate-limit policy
The permitted request count and time window should reflect the client’s real behavior. A server-rendered frontend with shared caching may need fewer upstream calls than a mobile application refreshing several collections. Clients should read rate-limit information, back off after a 429 response and avoid retry loops.
REST caching reduces repeated data construction, but it does not make unbounded traffic harmless. API keys, rate limits and application-side caching work together to protect the WordPress installation.
Using webhooks responsibly
The import and entity-sync webhooks can tell another system that WordPress data changed. The receiving endpoint should return quickly, validate the request according to the project’s security design and queue expensive follow-up work. Use the built-in test action during setup, then monitor the receiving application for delivery failures.
A search service might reindex imported posts after a completed session. A mobile backend might clear its own cache after entity synchronization. These event-driven workflows are more efficient than repeatedly polling for changes.
Template override workflow
Copy only the templates that genuinely need customization into the documented child-theme override directory. Keep the changes in version control and compare them when the plugin is updated. Overriding every file creates unnecessary maintenance; targeted overrides preserve more of the plugin’s upgrade path.
Use ACF sync when downstream templates or editors already depend on a defined field group. Confirm which values are authoritative before allowing manual edits, because synchronized SeatGeek data may replace changes to mapped fields.
Operational checks before launch
- Test authenticated, unauthenticated and rate-limited requests.
- Confirm cache hits, misses and stale behavior.
- Verify webhook delivery and receiving-system error handling.
- Check custom templates with long titles, missing images and empty results.
- Review multisite and domain registration assumptions.
When Developer is the right licence
Choose Developer when another application must consume events or entities, when clients need authenticated and rate-limited access, when imports must notify another system, or when the active theme requires controlled template replacement. If the requirement is a high-volume WordPress event portal with directories and automation but no external API, Business may be sufficient.
Developer still includes the complete frontend system: live listings, imports, Display on Pages with live preview, five layouts, performer and venue directories, caching, scheduled automation, exports, shortcodes, widgets and affiliate tracking.
Build a custom SeatGeek and WordPress integration →
