Pawpaw Analytics
Pawpaw Analytics

Find a Time — docs

Drive the whole flow from your own AI assistant — or straight from code. It's a small JSON API with no sign-in and no authentication. Back to the app.

Use it with your AI assistant

Copy this prompt, paste it into ChatGPT, Claude, or any assistant that can browse, and fill in the bracket. It will read the API below and set the event up for you, then hand back the links to share. 


        
        

          On a poll you've been invited to, or a results page, you'll find a
          matching one-click prompt for responding or picking the best time.
        

      

    


    

      Everything below is relative to https://meet.pawpawanalytics.com.
      Bodies and responses are JSON; no endpoint needs a key or a cookie. There's
      also a plain-text version of this reference at
      /llms.txt for agents that prefer it.
    


    

      
Create an event

      

        Describe the grid with a high-level availability object and the
        server expands it into slots. The response carries _links (the
        invite and results pages to share) and _actions (the URLs below).
      

      
POST /events
Content-Type: application/json

{
  "title": "Board Meeting",
  "timezone": "America/Chicago",   // IANA name
  "slot_minutes": 30,              // 15 | 30 | 60
  "availability": {
    "start_date": "2026-06-08",
    "end_date":   "2026-06-12",
    "weekdays":   [1, 2, 3, 4, 5], // ISO 1=Mon..7=Sun, or "weekdays"|"everyDay"|"weekends"
    "window_start": "09:00",       // 24h wall-time in the event's timezone
    "window_end":   "17:00"        // exclusive end
  }
}

      

        Already have exact instants? Send "slot_starts": ["<UTC ISO-8601>", …]
        instead of availability.
      

    


    

      
Read an event

      

        A share link looks like /e/<event_id>; the event id is that UUID.
        starts_at is UTC — render it in the returned timezone to
        label each slot.
      

      
GET /events/<event_id>
→ { title, timezone, slot_minutes, slots: [{ slot_id, starts_at }], _actions: {…} }

    


    

      
Submit availability

      

        Pick slot_ids from the event's slots. Submit exactly
        once — responses are not de-duplicated.
      

      
POST /events/<event_id>/responses
Content-Type: application/json

{ "name": "Ada Lovelace", "slot_ids": ["<slot_id>", …] }

    


    

      
See who overlaps

      

        The live heatmap behind the results page: per-slot counts and the names
        free in each.
      

      
GET /events/<event_id>/density
→ { slots: [{ slot_id, starts_at, count, names: [...] }] }

    


    

      Built by Pawpaw Analytics. No
      account, no tracking of who's scheduling what — the share link is the only
      key.