Spotka: meet people in Warsaw around the activities you love

• Ideas — Things to do in the city, picked for this member: exhibitions, gigs, markets, walks. Use when they ask what is on, what to do this weekend, or for something to suggest to a friend.
• Events — Events OTHER Spotka members are hosting that suit this member — small gatherings they could join. Not their own events. The API prefers this member's ranked suggestions by default, then searches the broader By Others browse pool when that deck is empty or when you send a text query. Other filters narrow whichever pool was loaded, so `deck_size` tells you how many rows were considered before filtering. If it comes back empty, read `empty.reason`: still_ranking (ask again shortly), no_inventory (n
• My Events — This member's own events: the ones they host, the ones they joined, and invitations waiting for an answer. Use before creating or inviting, to see what already exists.
• Create Event — Create an event this member will host. when= accepts a weekday phrase such as "next Saturday at 6pm", an ISO instant such as 2026-08-22T18:00:00+02:00, a date-and-time with no offset such as "2026-09-26 18:00" (18:00 Europe/Warsaw, the same as typing 6pm), or a dated wall-clock with an IANA zone such as "2026-09-10 12:00 Europe/Warsaw". starts_at/ends_at may be sent as direct ISO fields instead of when=. Leave both when= and starts_at out to mark the time as to-be-decided (time_tbd) — do not inv
• Update Event — Change an event this member hosts — a wrong time, a new venue, a reworded description, or publish=true to publish a draft once when and where are set. The event must be the full event id; a truncated id is invalid_event_id. A when-less and starts_at-less draft stays time-not-set (time_tbd) rather than inventing a start. A PARTIAL update: pass only the fields that change and everything else is left exactly as it is. If the supplied time cannot be applied the whole call fails and the other fields
• Profile — This member's own profile. Returns `public` (what other Spotka members can see) and `private` (their own context: interests, dietary needs, allergies, languages, what they are focused on right now). Read it BEFORE suggesting events or writing an invitation — it is what makes a suggestion personal. Use the private half to decide what to suggest; never copy it into an invitation, a message, or anything another member will read.
• Update Profile — Change this member's own profile. Pass only the fields that change; everything else is left exactly as it is. Ask the member before calling this — it is their identity, and some of it is visible to other members. Fields that cannot be set this way (email, phone, role, location coordinates, app settings) are refused by name rather than silently ignored.
• Notification Settings — Which notifications this member gets from Spotka, and whether anything can actually deliver them. Spotka sends on two rails, `push` and `email`, and each notification carries a SEPARATE value per rail under `channels` — a member can want the weekly ideas as a push and not as an email. Each says whether it is on, whether that is the member's own choice or Spotka's default (`using_default`), and which apps it applies to. `delivery.push.devices` is how many devices are registered: at zero, NO PUSH
• Update Notification Settings — Turn this member's notifications on or off. Only the settings you name change. ALWAYS ask the member before calling this: a notification switched off is invisible until the thing it would have announced has already been missed. Pass `settings` as keys from notification_settings mapped to true, false, or "default" — where "default" clears their choice so the setting follows whatever Spotka ships with, which is the only way back once an explicit value is stored. Naming a notification changes EVERY
• Calendar — This member's Spotka agenda: events they host and events they joined, soonest first, with exact start times as ISO instants. Use it for "what have I got on?", before suggesting a new event, or to check for a clash. Events whose time is not agreed yet come back separately in `undated` — never treat those as scheduled, and never tell a member they are busy because of one.
• Activity History — What this API has changed on this member's account, newest first: which action, what it touched, and whether it worked. Use it to answer "what did you just do?" or to check a result you are unsure of. It is a RECORD, not an undo log — there are no undo tokens. To reverse something, call the opposite action: leave undoes join, respond again changes an answer, revoke_invite takes back an invitation, delete_event removes an unpublished draft. An archived event cannot be un-archived; that is a Spotk
• Revoke Invite — Take back an invitation this member sent. Pass invite= as the id do=event lists — that is enough on its own for a pending email invite; event= is not required. The invitation stops accepting a reply. It does NOT unsend the email — that is already in the recipient's inbox and cannot be recalled, so if it matters, tell the member to say something. Confirm with them before calling.
• Inbox — What is waiting for this member: conversations with unread messages, and event invitations waiting for an answer. unread_total counts every unread conversation, not just this page — limit pages the list only. Reading it marks NOTHING read — the member's unread badges are untouched. Fern conversations are flagged with is_fern so you do not mistake Spotka's own assistant for one of their friends.
• Conversation — One conversation's messages, oldest first. Does NOT mark anything read, so you can summarise an inbox without clearing badges for messages the member never saw. oldest_at is the cursor for `before=` (there is no since=). When has_more is true, pass before=<oldest_at> for older messages.
• Mark Read — Mark a conversation as read. Only call this when the member has ACTUALLY seen the messages — reading a thread on their behalf is not the same as them reading it.
• Send Message — Send a message as this member. This writes to a REAL person in their name and cannot be unsent — always confirm the exact wording with them first. Most keys cannot do this: messaging is off by default, and a key without it gets a clear refusal (check the capabilities tool). Only replies in a conversation they already have, or writes to Fern; it cannot start a conversation with a stranger.
• Invite — Invite people to an event by email. Give `event` for one that exists, or give the create_event fields instead to create it and invite in the same call. A person is listed in invited only when a pending invitation they can see and answer was created; otherwise the call names why. This SENDS REAL EMAIL in the member's name — always confirm the recipients with them first. The daily recipient allowance is charged only once the event is settled, so a wrong event id costs nothing. When creating the ev
• Event — One event in full. The event must be the full event id; a truncated id is invalid_event_id. Host view includes lifecycle (published / pending_proposal / calendared), held_guest_count, calendared_guest_count, guest_seats_remaining, guest_states (interested_with_held_seat / proposed_time / calendared), calendared_attendees (same as confirmed — only guests on an upcoming calendared encounter), interested_count / interested (includes a soft respond decision=interested RSVP), and allowed_actions. A g
• Join — Take a seat at an event another member is hosting. A host cannot join their own event, and the event must be published. Optional starts_at/ends_at propose a time to the host (not the event's own start). An unreadable ISO value is refused rather than forwarded mangled.
• Leave — Give up a seat previously taken at an event. A host cannot leave their own event (cannot_leave_own_event). Archive or delete it instead. An event id that does not exist returns event_not_found (404), not candidate_stale — refresh cannot find it. The rest of the member's event suggestions stay.
• Respond — Answer something addressed to this member: accept, decline, or interested. Accept takes a seat; interested is a soft RSVP that records the person on the host's interested list without taking a seat (task #2512 / #2500). Changing interested to accept takes a seat; it is not already_responded. As the host instead, pass `guest` and decision approve/decline only for a pending time proposal (guest_states proposed_time / allowed_actions includes approve_proposal). Do not approve a guest who already ho
• Archive — Retire an event this member hosts. The event must be the full event id; a truncated id is invalid_event_id. This is what removes it from everyone's list. An event this member cannot see is event_not_visible, not invitation_not_found.
• Delete Event — Delete an unpublished draft this member hosts. The event must be the full event id; a truncated id is invalid_event_id. A published event, or one with guests, must be archived instead. Deleting an id that is already gone returns event_not_found — retrying a successful delete is safe. An event this member cannot see is event_not_visible, not invitation_not_found.
• Report Bug — Tell the Spotka team something in Spotka is broken. Use it when a call you made did not do what it should, or the member says something is wrong — you were there for it, so you can describe it better than they can. It files the same report the app's own "Report a bug" files. Default is no auto-fix. Pass autofix=true on a clear bug to send it to a coder. When you have them, send product_url, app_version, platform, and a screenshot as a data URL — that is what a coder uses to fix it on the first t
• Report Feature — Ask the Spotka team for something Spotka does not do yet. Use it when the member wants something that is missing rather than broken. Same queue and same rule as report_bug: a person reads it and decides, nothing is built automatically, and nothing here makes a request urgent. Tell the member the request was passed on; never tell them it will be built, or when. Say what they want AND what they are trying to achieve — the second part is what makes a request answerable.

Showing the first 25 tools — full list and schemas: Directory API.