# Attendease (EventUp Planner)

> Attendease — now EventUp Planner following its acquisition by Tripleseat — is an event and meeting management platform for planning, promoting, and running virtual, in-person, and hybrid events (conferences, webinars, roadshows, product launches). It publishes a public developer API in two tiers plus first-party JavaScript and Ruby SDKs.

This file was generated by the API Evangelist enrichment pipeline from the public developer documentation, the help center, and package registries. Method: generated. Source: https://developer.attendease.com/ (last refreshed 2026-08-13)

## Access up front

- API access is an **Enterprise-plan entitlement**. The plans table lists "API Access" only under Enterprise (https://eventupplanner.com/plans-and-pricing/).
- The Organization API is offered to Enterprise customers only, and its credentials are created, deleted and regenerated by contacting support — not self-serve.
- Event API access tokens ARE self-serve: a UUID token named "default" is auto-created for every event under Event -> Integrate -> Access Tokens, and additional named tokens can be added or removed at any time.
- The reference documentation itself is fully public and requires no login.

## APIs

- [Attendease Developer API](https://developer.attendease.com/): Developer portal and reference for both API tiers. A static Slate single-page document — there is no OpenAPI, Swagger, GraphQL, AsyncAPI or MCP contract published anywhere on the provider's hosts.
- Organization API (`/api/v2/`): Organization-wide REST API — business units, events, members, attendees, session attendance, check-ins, partners, contact lists. Base URL pattern: https://your-org.attendease.org/api/v2/. Auth: HMAC-SHA1 request signing (`Authorization: APIAuth access_key:signature`, RFC 1123 Date within 15 minutes).
- Event API: Event-scoped REST API — event properties, sessions, session instances, presenters, surveys, sponsors, rooms, venues, filters, content. Base URL pattern: https://your-event.attendease.com/api/ (the subdomain is the one chosen when the event was created). Auth: attendee/event tokens (`X-Attendee-Token`, `X-Event-Token`, or the same values as query params) or HTTP Basic with attendee email/password.

## Conventions

- Media type: application/json; resource paths carry a .json suffix.
- Pagination: page-number style; params `page` + `records_per_page` (1-100, default 50); pagination envelope with total_records, num_records, page_size, page_count, page. The session_attendees (Multi-session) call is the one documented exception — it is not paginated.
- Metadata: custom fields filtered via `?meta[key]=value` (multiple meta params AND together) and written in a `meta` object on the resource.
- Errors: custom JSON envelope `{ "error": "message" }`; 422 returns a field-keyed `errors` object. Not RFC 9457.
- Idempotency: not documented, not supported.
- Rate limits: no enforced limits, no quotas and no rate-limit response headers are published. HTTP 429 is a documented status. One advisory exists: leave at least 300 seconds between `session_attendance` calls.
- Transport: HTTPS required; plain HTTP calls fail.

## Operational surface

- Status page: https://status.attendease.com/ (StatusCake public report; uptime history and announcements, JS-rendered, no feed or JSON endpoint).
- Deprecation policy: none published. No Sunset/Deprecation headers.
- SLA: none published.
- Webhooks / events / streaming: none. The developer docs never mention webhooks and a help-center search returns zero webhook articles.
- Compliance: accessibility only — VPAT certification, WCAG 2.1 Level AA templates, ADA (https://eventupplanner.com/accessibility/). No SOC 2, ISO 27001, PCI DSS or HIPAA attestation is published.
- No /.well-known/ documents are served on any host (security.txt, openid-configuration, oauth-authorization-server, api-catalog, ai-plugin.json, agent-card.json all miss).

## SDKs and packages

Every published first-party client is stale — check dates before depending on one.

- [attendease (npm)](https://www.npmjs.com/package/attendease): Official JavaScript/Node SDK. v1.0.1, published 2017-01-30.
- [attendease-blocks (npm)](https://www.npmjs.com/package/attendease-blocks): CMS Blocks. v0.4.63, published 2017-03-05.
- [attendease (RubyGems)](https://rubygems.org/gems/attendease): v0.0.0, published 2014-12-05 — a placeholder, not a working client.
- [jekyll-attendease (RubyGems)](https://rubygems.org/gems/jekyll-attendease): Jekyll plugin for event websites. v0.9.9.7, published 2023-10-19. Its source repository now returns 404.
- [attendease-sdk-ruby (GitHub)](https://github.com/attendease/attendease-sdk-ruby): the maintained Ruby SDK, last pushed 2025-01-29. Never published to RubyGems — install from git.
- [GitHub organization](https://github.com/attendease)

## Integrations

Slack, Salesforce, Marketo, HubSpot and Stripe integrations are documented in the help center and are Enterprise entitlements. See https://eventupplanner.com/integrations/

## Resources

- [Developer portal](https://developer.attendease.com/)
- [Plans and pricing](https://eventupplanner.com/plans-and-pricing/)
- [Sign in / dashboard](https://dashboard.attendease.com/)
- [Support / help center](https://eventupplanner.zendesk.com/hc/en-us)
- [Status](https://status.attendease.com/)
- [Blog](https://eventupplanner.com/blog/)
- [Accessibility](https://eventupplanner.com/accessibility/)
- [Terms of use](https://eventupplanner.com/terms-of-use/)
- [Services agreement](https://eventupplanner.com/services-agreement/)
- [Privacy policy](https://eventupplanner.com/privacy-policy/)