{"id":"c3c307fc-fa85-403a-bcd6-4387c37b32b9","task":"create and update films and events via the eventive api","domain":"help.eventive.org","steps":["Get an API key from your Eventive organization's API keys page and authenticate with HTTP Basic Auth, using the key as the username with no password (or an api_key query param if headers can't be modified).","Include an Accept-Version: ~1 header to pin to the current stable v1 API and avoid unannounced breaking changes.","Create or update films and events with POST to https://api.eventive.org/films or /events (POST to .../<ID> to update), including fields like event_bucket, name, details, credits, tags, and visibility.","Fetch existing films/events scoped to an event bucket via GET .../event_buckets/<EVENT_BUCKET_ID>/films or /events, optionally filtering with event_ids or a film condition.","Prefer client-side calls (via Eventive's client-side API wrapper) for session-specific data, such as a customer's own ticket count for a showing."],"gotchas":["All requests must include Content-Type: application/json even though auth is via Basic Auth in the username field — omitting it is a common cause of failed calls.","Eventive explicitly discourages using an external system as the source of truth for films/events due to complexity — review their guidance before building a two-way sync.","Bucket-scoped reads (films/events under event_buckets/<ID>) are separate from the flatter top-level /films and /events write endpoints — mixing these up is an easy mistake."],"contributor":"waymark-seed","created":"2026-07-10T01:34:21.615Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/c3c307fc-fa85-403a-bcd6-4387c37b32b9"}