Build on PartyIRL.

A REST API and an MCP server for real-life events: create with one prompt, RSVP, search your city. Free, keyed to your account, same rules as the app.

Step 1 · Get your key

Go to your account → DEVELOPER section.
Name a key and hit CREATE KEY.
Copy the pk_live_… value immediately. It's shown exactly once. We keep a hash, not the key.

A key acts as YOU: it can publish events and RSVP under your name. Treat it like a password; revoke it from the same screen the moment it leaks.

Step 2 · Authenticate

Every request carries the key as a Bearer token. Base URL: https://api.partyirl.com

Authorization: Bearer pk_live_YOUR_KEY

Unknown or revoked keys get 401. Errors are always JSON: { "error": { "code", "message" } }.

REST reference

You

GET/v1/me

Who this key acts as.

curl https://api.partyirl.com/v1/me \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{
  "id": "cm…", "handle": "joel", "displayName": "Joel",
  "avatarUrl": null, "avatarColor": "lime",
  "createdAt": "2026-08-09T23:00:16.874Z",
  "hostedEvents": 12, "followers": 3
}

PATCH/v1/me

Edit your profile: handle, display name, initials-avatar color, or avatar photo.

handle: · 3–24 lowercase letters, numbers, or underscores. Availability-checked; one change every 30 days
displayName: · 1–50 chars. Shows on guest lists and your events; one change every 14 days
avatarColor: · tangerine · bubble · lime · pool · paper · soft · null (back to default)
avatarUrl: · CDN avatar url from /v1/uploads, or null to remove the photo

curl -X PATCH https://api.partyirl.com/v1/me \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "handle": "joel_thomas", "displayName": "Joel Thomas", "avatarColor": "pool" }'

Response

{ …same shape as GET /v1/me, updated }

Events

Everything the app's create and edit forms can do. Host-only actions check ownership exactly like the site.

GET/v1/events

Your calendar: events you host plus events you RSVP'd to.

curl https://api.partyirl.com/v1/events \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{
  "hosted":    [{ "slug": "…", "title": "…", "startsAt": "…",
                  "timezone": "…", "categories": ["…"],
                  "visibility": "…", "city": "…", "archived": false }],
  "attending": [{ …same fields, plus "rsvpStatus": "IN",
                  "guestCount": 0 }]
}

GET/v1/events/:slug

One event, full detail. Gated addresses only appear once you've RSVP'd (or host it). guestList follows the host's guestListVisibility and is null when you're not permitted — the counts are always there. It carries names and faces only: no phone number, phone tail, or email is ever returned for anyone but yourself.

slug: · the last path segment of a partyirl.com/e/<slug> URL

curl https://api.partyirl.com/v1/events/taco-night-x7k2p9 \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{
  "slug": "taco-night-x7k2p9", "title": "TACO NIGHT",
  "description": "…", "startsAt": "…", "timezone": "…",
  "categories": ["FOOD_DRINK", "PARTY"],
  "locationName": "…", "address": null, "city": "…",
  "capacity": 15, "goingCount": 9, "waitlistCount": 0,
  "guestListVisibility": "CONFIRMED_GUESTS",
  "guestList": [{ "id": "cm…", "displayName": "Maya",
                  "avatarUrl": null, "avatarColor": "pool",
                  "guestCount": 1, "status": "IN" }],
  "host": { "handle": "…", "displayName": "…" },
  "url": "https://partyirl.com/e/taco-night-x7k2p9",
  "myRsvp": { "status": "IN", "guestCount": 0 }
}

POST/v1/events

Create + publish an event. Send a prompt and the AI drafts everything: title, copy, time, poster. Or send a full draft object to skip the AI.

prompt: · the event in your own words (3–500 chars)
vibe: · optional: chill · hype · fancy. Locks the tone
timezone: · optional IANA zone for relative dates (default America/Chicago)
visibility: · optional: PUBLIC (default, in Discover) · UNLISTED · PRIVATE
guestListVisibility: · optional: HOST_ONLY · CONFIRMED_GUESTS (default) · EVERYONE. Who sees WHO'S COMING. The headcount is always public either way
draft: · optional: a full event draft object instead of prompt: title, description (markdown), startsAt/endsAt/timezone, locationName, city/state, hideAddressUntilRsvp, capacity, waitlistEnabled, maxGuestsPerRsvp, vibe, 1–3 categories (a legacy single category string is accepted), full poster params
recurrence: · optional: { frequency: DAILY · WEEKLY · BIWEEKLY · MONTHLY, endsOn? }. Makes it repeat
questions: · optional: RSVP questionnaire (same shape as PUT …/questions)
address: · optional street address (gated by hideAddressUntilRsvp)
requireName: · optional: guests must give a real name
commentsEnabled / commentsPrivate: · optional wall settings (on/off · confirmed-guests-only)
imagePoster: · optional full-image poster ({url, thumbUrl, width, height} from /v1/uploads)

curl -X POST https://api.partyirl.com/v1/events \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "rooftop movie night saturday 8pm, byo blanket, 20 ppl",
    "vibe": "chill",
    "timezone": "America/Los_Angeles",
    "visibility": "UNLISTED"
  }'

Response

201 Created
{
  "slug": "rooftop-movie-night-a1b2c3",
  "url": "https://partyirl.com/e/rooftop-movie-night-a1b2c3",
  "title": "ROOFTOP MOVIE NIGHT",
  "startsAt": "2026-08-15T03:00:00.000Z",
  "timezone": "America/Los_Angeles",
  "visibility": "UNLISTED"
}

POST/v1/events/:slug/rsvp

RSVP as yourself. Repeat calls replace the previous answer; OUT cancels. A full event with a waitlist turns IN into WAITLIST. Check the returned status.

status: · IN · MAYBE · OUT
guestCount: · optional plus-ones, 0–10 (default 0)

curl -X POST https://api.partyirl.com/v1/events/taco-night-x7k2p9/rsvp \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "status": "IN", "guestCount": 1 }'

Response

{ "slug": "taco-night-x7k2p9", "status": "IN", "guestCount": 1 }

PATCH/v1/events/:slug

Partial edit. Send only the fields to change. Same fields as the app's edit form: title, description, startsAt (guests get a date-change banner), endsAt, timezone, locationName, address, city, state, hideAddressUntilRsvp, capacity, waitlistEnabled, maxGuestsPerRsvp, categories, requireName, commentsEnabled, commentsPrivate, guestListVisibility, visibility, poster.

curl -X PATCH https://api.partyirl.com/v1/events/taco-night-x7k2p9 \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "capacity": 30, "commentsPrivate": true }'

Response

{ …the updated event, same shape as GET /v1/events/:slug }

POST/v1/events/:slug/archive

Archive (or restore) THIS date only. Reversible. The link keeps working, RSVPs close, it leaves Discover. On a recurring event the series keeps going.

archived: · true (default) to archive · false to restore

curl -X POST https://api.partyirl.com/v1/events/taco-night-x7k2p9/archive \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "archived": true }'

Response

{ "slug": "taco-night-x7k2p9", "archived": true }

DELETE/v1/events/:slug

Permanently delete THIS date. The guest list, answers, and passes go with it. Requires an explicit confirm.

confirm: · must be true. There is no undo

curl -X DELETE https://api.partyirl.com/v1/events/taco-night-x7k2p9 \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "confirm": true }'

Response

{ "slug": "taco-night-x7k2p9", "deleted": true }

Recurrence schedules

Address a recurrence through any occurrence slug. A Series is the community; this endpoint only changes the repeating calendar schedule.

PATCH/v1/events/:slug/recurrence

Apply fields to EVERY upcoming occurrence (each keeps its own date). Send only what you mean to push. the explicit field list is the app's "only what you changed" save; sending everything is its OVERRIDE mode.

curl -X PATCH https://api.partyirl.com/v1/events/run-club-week-3/recurrence \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "capacity": 40, "locationName": "Festival Beach" }'

Response

{ "slug": "run-club-week-3", "updatedOccurrences": 8,
  "fields": ["capacity", "locationName"] }

POST/v1/events/:slug/recurrence/end

Stop the repeat (no new dates are created). futureAction decides what happens to already-created upcoming dates. Requires confirm.

futureAction: · KEEP (default) · ARCHIVE · DELETE
confirm: · must be true. Ending a recurrence can't be undone

curl -X POST https://api.partyirl.com/v1/events/run-club-week-3/recurrence/end \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "futureAction": "ARCHIVE", "confirm": true }'

Response

{ "slug": "run-club-week-3", "ended": true,
  "futureAction": "ARCHIVE", "affectedOccurrences": 8 }

Questions & answers

GET/v1/events/:slug/questions

The RSVP questionnaire guests see.

curl https://api.partyirl.com/v1/events/taco-night-x7k2p9/questions \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{ "slug": "…", "questions": [{ "id": "…", "position": 0,
  "type": "SINGLE_SELECT", "label": "Coming for…",
  "required": true, "options": ["Tacos", "Margs", "Both"] }] }

PUT/v1/events/:slug/questions

Replace the questionnaire (host only; copies to upcoming occurrences on a series). Answers to removed questions are deleted. Max 15.

questions[].type: · SHORT_TEXT · LONG_TEXT · SINGLE_SELECT · MULTI_SELECT · NUMBER · DATE · DATETIME · URL · EMAIL · PHONE · YES_NO
questions[].label: · the question (≤120 chars); helpText, required, options (2+ for SELECT types), config optional

curl -X PUT https://api.partyirl.com/v1/events/taco-night-x7k2p9/questions \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "questions": [{ "type": "YES_NO", "label": "Bringing a dish?",
        "required": true }] }'

Response

{ "slug": "…", "questions": [ …with server ids ] }

GET/v1/events/:slug/answers

Host only: every guest's answers, grouped by guest.

curl https://api.partyirl.com/v1/events/taco-night-x7k2p9/answers \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{ "slug": "…", "answers": [{ "guest": "Maya", "handle": "maya",
  "status": "IN", "answers": [{ "questionId": "…", "value": true }] }] }

Guests

PartyIRL never hands out other people's contact details. No endpoint returns a guest's phone number, phone tail, or email — not to hosts, not to anyone. You get names, avatars, RSVP state, and the answers they gave your questions.

GET/v1/events/:slug/guests

Host only: the guest list. Statuses, plus-ones, door check-ins, question answers, and whether you've blocked them. Contact details are never included — no phone number, no phone tail, no email. userId is the opaque account id POST /v1/blocks takes.

curl https://api.partyirl.com/v1/events/taco-night-x7k2p9/guests \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{ "slug": "…", "guests": [{ "rsvpId": "…", "userId": "cm…",
  "name": "Maya", "status": "IN", "guestCount": 1,
  "checkedIn": false, "blocked": false,
  "rsvpedAt": "…", "answers": [ … ] }] }

PATCH/v1/events/:slug/guests/:rsvpId

Host only: move a guest between IN, WAITLIST, and OUT. The host's word is final; promoting over capacity is allowed on purpose.

status: · IN · WAITLIST · OUT

curl -X PATCH https://api.partyirl.com/v1/events/taco-night-x7k2p9/guests/RSVP_ID \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "status": "IN" }'

Response

{ "slug": "…", "rsvpId": "RSVP_ID", "status": "IN" }

Hosts

Multi-host: roles are handed out BY PHONE NUMBER, so you can add the friend who works your door before they've ever opened PartyIRL — their access starts the moment that number signs in. OWNER = everything, including delete and transfer · CO_HOST = edits the event, runs the guest list and the wall, works the door · DOOR = checks people in and reads the guest list for that, nothing else. Reading the list needs edit access; changing it is owner-only. Phone numbers always come back masked.

GET/v1/events/:slug/hosts

Everyone with a role on the event, owner first. claimed:false means they were invited by phone and haven't signed in yet. id is what the PATCH and DELETE below take (the owner's row isn't one of them).

curl https://api.partyirl.com/v1/events/taco-night-x7k2p9/hosts \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{ "slug": "…", "hosts": [
  { "id": "owner:cm…", "role": "OWNER", "userId": "cm…",
    "displayName": "Joel", "handle": "joel", "avatarUrl": null,
    "avatarColor": "lime", "phoneMasked": "•••• 9991",
    "claimed": true, "createdAt": "…" },
  { "id": "cm…", "role": "DOOR", "userId": null,
    "displayName": null, "handle": null,
    "phoneMasked": "•••• 0100", "claimed": false, "createdAt": "…" }
] }

POST/v1/events/:slug/hosts

Owner only: give a phone number a role. No account needed — pending:true means the invite is waiting on their first sign-in. On a recurring event this covers every upcoming date and rides along to dates created later. Posting a number that's already on the list changes its role instead of duplicating it.

phone: · any format with a country code; a bare 10-digit US number gets +1
role: · CO_HOST (runs the party with you) · DOOR (check-ins only)

curl -X POST https://api.partyirl.com/v1/events/taco-night-x7k2p9/hosts \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "phone": "+15125550100", "role": "DOOR" }'

Response

201 Created
{ "slug": "…", "host": { "id": "cm…", "role": "DOOR",
    "userId": null, "phoneMasked": "•••• 0100", "claimed": false, … },
  "datesAffected": 8, "pending": true }

PATCH/v1/events/:slug/hosts/:id

Owner only: move someone between CO_HOST and DOOR. Applies across a series' upcoming dates.

role: · CO_HOST · DOOR

curl -X PATCH https://api.partyirl.com/v1/events/taco-night-x7k2p9/hosts/HOST_ID \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "role": "CO_HOST" }'

Response

{ "slug": "…", "host": { …updated… }, "datesAffected": 8 }

DELETE/v1/events/:slug/hosts/:id

Owner only: take the keys back. Access ends immediately across every upcoming date, and they're never notified. Their RSVP, if they have one, is untouched.

curl -X DELETE https://api.partyirl.com/v1/events/taco-night-x7k2p9/hosts/HOST_ID \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{ "slug": "…", "removed": true, "datesAffected": 8 }

POST/v1/events/:slug/transfer

Owner only, ONE-WAY, confirm-gated: hand the event to a phone number. You drop to CO_HOST — you keep edit and guest access but lose delete, transfer, and the host list, and only the new owner can hand it back. If that number has no account yet the transfer parks (pending:true) and completes at their first sign-in; until then DELETE the same path to call it off. A recurring event moves as a whole: this date, every upcoming date, and the series itself. Past dates never move.

phone: · the new owner's number, with country code
confirm: · must be true — you can't take it back

curl -X POST https://api.partyirl.com/v1/events/taco-night-x7k2p9/transfer \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "phone": "+15125550100", "confirm": true }'

Response

{ "slug": "…", "pending": false, "phoneMasked": "•••• 0100",
  "eventsTransferred": 8, "eventsScoped": 8,
  "newOwner": { "id": "cm…", "displayName": "Maya", "handle": "maya" } }

DELETE/v1/events/:slug/transfer

Owner only: call off a transfer that's still waiting on someone's first sign-in. Once it lands there is nothing to cancel — the new owner decides from there.

curl -X DELETE https://api.partyirl.com/v1/events/taco-night-x7k2p9/transfer \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{ "slug": "…", "cancelled": 8 }

GET/v1/events/:slug/permissions

What this key may do on the event: role (OWNER · CO_HOST · DOOR · null) plus explicit capability flags. Check it before offering an action you'd only be refused at.

curl https://api.partyirl.com/v1/events/taco-night-x7k2p9/permissions \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{ "slug": "…", "permissions": {
  "role": "DOOR", "canEdit": false, "canManageGuests": false,
  "canCheckIn": true, "canManageCollaborators": false,
  "canModerateWall": false, "canDelete": false,
  "canTransfer": false, "canPostAsHost": false } }

POST/v1/events/:slug/checkins

Work the door: mark a guest as arrived, or undo it with checked:false. Open to the owner, co-hosts, and DOOR collaborators. Idempotent — checking someone in twice is one arrival.

userId: · the guest's opaque account id, from the guest list
checkedIn: · default true; false undoes a check-in

curl -X POST https://api.partyirl.com/v1/events/taco-night-x7k2p9/checkins \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "userId": "cm…" }'

Response

201 Created
{ "slug": "…", "userId": "cm…", "checkedIn": true }

Blocks

Your own door policy, across every event you host. Nothing to do with platform moderation — it never touches anyone's account, and the person blocked is never notified.

GET/v1/blocks

Everyone you've blocked from your events, newest first. reason is your own private note.

curl https://api.partyirl.com/v1/blocks \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{ "blocked": [{ "userId": "cm…", "handle": "maya",
  "displayName": "Maya", "avatarUrl": null,
  "avatarColor": "pool", "reason": "no-shows",
  "createdAt": "2026-08-11T02:14:00.000Z" }] }

POST/v1/blocks

Block someone from every event you host. Immediately removes their RSVPs on your UPCOMING events (the seats and plus-ones go back to the pool) and hides their comments on your events. Past events keep their history. Idempotent — re-posting just updates the reason.

userId: · opaque account id, from a guest list row
reason: · optional private note (≤300 chars). Never shown to them

curl -X POST https://api.partyirl.com/v1/blocks \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "userId": "cm…", "reason": "kept no-showing" }'

Response

201 Created
{ "blocked": true, "userId": "cm…", "displayName": "Maya",
  "rsvpsRemoved": 2, "seatsFreed": 3, "commentsHidden": 4 }

DELETE/v1/blocks/:userId

Reopen your door. They can RSVP and post again — but the RSVPs the block removed are NOT restored and the comments it hid are NOT unhidden.

curl -X DELETE https://api.partyirl.com/v1/blocks/cm… \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{ "blocked": false, "userId": "cm…" }

Uploads

POST/v1/uploads

Import an image (≤10 MB). Metadata stripped, resized, re-encoded to CDN WebP. Send JSON {url} for a server-side fetch of a public https image, OR multipart/form-data with a "file" field. kind=poster (default, ≤1600×2000; use as poster backgroundImageUrl or an imagePoster) · kind=avatar (512px square; use with PATCH /v1/me).

curl -X POST https://api.partyirl.com/v1/uploads \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://example.com/flyer.jpg", "kind": "poster" }'

# or multipart:
curl -X POST https://api.partyirl.com/v1/uploads \
  -H "Authorization: Bearer pk_live_YOUR_KEY" \
  -F "file=@flyer.jpg" -F "kind=poster"

Response

201 Created
{ "kind": "poster",
  "url": "https://cdn…/posters/aB3….webp",
  "thumbUrl": "https://cdn…/posters/aB3…-sm.webp",
  "width": 1600, "height": 2000 }

Discover

GET/v1/discover

Search upcoming PUBLIC events. All filters optional.

query: · free text. Matches title, description, venue, category names
category: · PARTY · FOOD_DRINK · MUSIC_SHOWS · SPORTS_FITNESS · GAMES · ART_CULTURE · TECH_NETWORKING · OUTDOORS · MARKET_POPUP · OTHER. Matches events whose 1–3 tags contain it
city: · exact city name, case-insensitive

curl "https://api.partyirl.com/v1/discover?query=tacos&city=Austin" \
  -H "Authorization: Bearer pk_live_YOUR_KEY"

Response

{
  "events": [{ "slug": "…", "title": "…", "startsAt": "…",
               "timezone": "…", "categories": ["…"],
               "locationName": "…", "city": "Austin", "state": "TX",
               "goingCount": 12 }]
}

MCP server for your AI

Point Claude (or any MCP client) at https://api.partyirl.com/mcp (Streamable HTTP, same Bearer key) and it can throw parties for you.

Tools

create_event: · prompt → AI draft, or a full draft object; recurrence, questions, wall settings, guest-list visibility, visibility
update_event: · partial edit; apply_to_recurrence pushes the same fields to every upcoming date
set_poster: · generated poster params (palette, layout, fonts, bg photo) or a full uploaded image
set_questions: · replace the RSVP questionnaire
upload_image: · public image URL → CDN webp (kind: poster | avatar)
end_recurrence: · stop the repeat; KEEP/ARCHIVE/DELETE upcoming dates (confirm-gated)
archive_event: · archive or restore one date (reversible)
delete_event: · permanently delete one date (confirm-gated)
guest_list: · host view: statuses, plus-ones, check-ins, answers (never contact details)
set_guest_status: · move a guest between IN / WAITLIST / OUT
check_in_guest: · mark a guest arrived at the door (owner, co-hosts, and DOOR)
list_hosts: · who runs an event: owner, co-hosts, door people, and pending phone invites
add_host: · give a phone number a CO_HOST or DOOR role — no account required
update_host_role: · move someone between CO_HOST and DOOR
remove_host: · take the keys back (silent)
transfer_event: · hand the event over to a phone; you drop to co-host (confirm-gated, one-way)
my_event_permissions: · your role and capability flags on one event
block_guest: · shut your door to someone across every event you host (silent; drops their RSVPs, hides their comments)
unblock_guest: · reopen the door — removed RSVPs and hidden comments do not come back
blocked_guests: · who you've blocked, with your private reason notes
list_my_events: · everything you host or RSVP'd to
get_event: · full details for one slug
rsvp: · IN / MAYBE / OUT, with plus-ones
search_events: · Discover search: query, category, city
profile: · read or update handle, name, avatar color, avatar photo

Claude Code

claude mcp add --transport http partyirl https://api.partyirl.com/mcp \
  --header "Authorization: Bearer pk_live_YOUR_KEY"

Claude Desktop

Settings → Developer → Edit Config, then add PartyIRL to claude_desktop_config.json (the mcp-remote bridge handles the Streamable HTTP connection):

{
  "mcpServers": {
    "partyirl": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.partyirl.com/mcp",
        "--header", "Authorization: Bearer pk_live_YOUR_KEY"
      ]
    }
  }
}

claude.ai (custom connector)

Settings → Connectors → Add custom connector.
Remote MCP server URL: https://api.partyirl.com/mcp
Where the connector asks for authentication, supply the header Authorization: Bearer pk_live_YOUR_KEY.

Rate limits

60 requests/minute per key (429 + Retry-After when you cross it). The app's own guardrails ride along: AI drafts are capped hourly and event creation daily. A key never gets more room than its owner.

Usage policy

Keys act as you, for things you'd do yourself: your events, your RSVPs, tools for your series. Don't spam feeds, scrape people's data, or automate RSVPs you don't mean. Moderation applies to API-created events exactly as in the app, and abusive keys (and accounts) get revoked.

Questions? It's early and things may move. Pin nothing to undocumented behavior.

PartyIRL · getting the night ready