Push events programmatically
The most accurate way to appear on SeeItEarly is to send us your events yourself. We surface partners by crawling their sites today, which can miss dates or get details wrong; events you send us show up exactly as you wrote them. Use a CSV drop now, or the write-only JSON API. Write-only on purpose, so we stay out of scraping wars. Already listed from your own site? You need neither: we pick up new events automatically, and you can email us any fix.
POST a single event
Write-only, key-gated, rate-limited per partner. Open to any partner: Trust 2+ (Featured/Sponsor) submissions auto-publish; Listed (Trust 1) submissions are reviewed first. Returns the created event id and its vet status.
/api/v1/partner/eventsLIVEcurl -X POST https://seeitearly.com/api/v1/partner/events \
-H "Authorization: Bearer sie_live_••••" \
-H "Content-Type: application/json" \
-d '{
"tmdb_id": 1011985,
"title": "The Mandalorian and Grogu",
"venue": "Dolby Theatre",
"city": "Hollywood, CA",
"start": "2026-05-19T19:30:00-07:00",
"rsvp_url": "https://gofobo.com/abc123",
"tier": "free",
"poster_url": null
}'{
"id": "evt_8fK2a",
"status": "pending_vet", // "published" for Trust 2+
"attribution": { "partnerId": "a24-screenings", "badge": true },
"dedup": "matched_none"
}title is required; tmdb_id is optional (we match the film from the title). Send start with its UTC offset and city as City, ST with a US state code; an event that has already started is refused. Leave poster_url null to fall back to the TMDB poster. Dedup runs on title + city + start (±30 min) against your existing events, so re-sending one we already list returns its id instead of a copy. Rate limit: 600 req/hour per key.Drop a spreadsheet
No engineering required. Send a CSV and we parse, dedup, and queue every row for vet.
tmdb_id,title,venue,city,start,rsvp_url,tier 1011985,The Mandalorian and Grogu,Dolby Theatre,"Hollywood, CA",2026-05-19T19:30:00-07:00,https://gofobo.com/abc,free ,Saturday Morning Cartoons 35mm,The Plaza Theatre,"Atlanta, GA",2026-06-14T11:00:00-04:00,https://eventbrite.com/xyz,paid
Columns map 1:1 to the JSON fields above. tmdb_id optional. A person reads every file: we reply with a parse report (rows accepted, deduped, and any that need a fix) within one business day.
Any partner can get a key
Any approved partner can be issued a key to send events directly; the CSV drop above needs no key at all. What your tier changes is routing, not access: Featured and Sponsor submissions auto-publish, Listed submissions are reviewed before they go live. The JSON API needs a little code, so the CSV drop is the no-code path.
We store only the key hash, keys are show-once on issue, and you can rotate them from your partner record. See API attribution policy →