REST API (v1)

The PepoSmart REST API lets your own backend list event types, read live availability, and create bookings on behalf of your users. Bookings made through the API are identical to bookings made on the booking page — the same confirmation emails, calendar invites, video links, reminders and AI meeting notes all apply.

Authentication

Every endpoint requires an API key, sent as a Bearer token. Create one in the app under Account → API Keys:

1. Go to app.peposmart.com/account/api-keys
2. Give the key a name that identifies the system using it, then Create key
3. Copy the key immediately — the full value is shown only once

Keys look like psk_live_…. Send them on every request:

Authorization: Bearer psk_live_xxxxxxxxxxxxxxxxxxxxxxxx

Scope of a key

A key is tied to the user account that created it. It can only see and book that account's event types. If you need to book across several hosts, either use a team event type (where PepoSmart assigns the host) or issue one key per host account.

Private event types are never returned or bookable through the API, even if you know the event id.

Rate limits

Exceeding a limit returns 429 with a Retry-After header giving the seconds to wait. Read and booking budgets are counted separately, so polling availability never eats into your booking allowance. If a production portal needs more headroom, contact support and we will raise it.

Booking flow

The three read-then-write calls, in order:

1. List event types to find the event id you want to book, and to learn what that event requires from the attendee.
2. Fetch availability for that event id and show the slots to your user.
3. Create the booking with the chosen slot and the attendee's details.

GET /api/v1/event-types

Lists the public, non-deleted event types belonging to the key's account.

curl https://app.peposmart.com/api/v1/event-types \
  -H "Authorization: Bearer psk_live_xxx"

Response 200

{
  "host": { "name": "Jordan Lee", "username": "jordan" },
  "eventTypes": [
    {
      "id": "evt_123",
      "title": "Discovery Call",
      "description": "A 30 minute intro call.",
      "durationMinutes": 30,
      "locations": ["google_meet"],
      "needsPhoneNumber": false,
      "needsPreferredLocation": false,
      "requiresPayment": false,
      "paymentAmountCents": null,
      "paymentCurrency": null,
      "eventType": "one-on-one",
      "hostCount": 1,
      "hostNames": ["Jordan Lee"],
      "bookingUrl": "https://app.peposmart.com/book/jordan/evt_123"
    }
  ]
}

GET /api/v1/availability/{eventId}

Returns bookable slots, with host schedules merged and existing bookings and external calendar busy blocks already removed.

curl "https://app.peposmart.com/api/v1/availability/evt_123?days=7&tz=Europe/London" \
  -H "Authorization: Bearer psk_live_xxx"

Response 200

{
  "eventId": "evt_123",
  "title": "Discovery Call",
  "durationMinutes": 30,
  "timezone": "America/New_York",
  "visitorTimezone": "Europe/London",
  "days": [
    {
      "date": "2026-09-01",
      "slots": [
        {
          "time": "09:00",
          "iso": "2026-09-01T13:00:00.000Z",
          "visitorDate": "2026-09-01",
          "visitorTime": "14:00"
        }
      ]
    }
  ]
}

Only days with at least one free slot are returned. timezone is the host's — date and time are expressed in it, and those are the two values you send back when booking. iso is the same instant in UTC, handy for sorting or rendering yourself.

POST /api/v1/bookings

Creates a confirmed booking.

curl -X POST https://app.peposmart.com/api/v1/bookings \
  -H "Authorization: Bearer psk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "eventId": "evt_123",
    "date": "2026-09-01",
    "time": "09:00",
    "attendee": {
      "name": "Jane Doe",
      "email": "[email protected]",
      "timezone": "Europe/London",
      "phoneNumber": "+44 20 7123 4567"
    },
    "location": "google_meet",
    "guestEmails": ["[email protected]"],
    "notes": "Wants to discuss the enterprise tier."
  }'

Response 201

{
  "booking": {
    "id": "bkg_789",
    "eventTitle": "Discovery Call",
    "startTimeIso": "2026-09-01T13:00:00.000Z",
    "durationMinutes": 30,
    "attendeeLocalTime": "Tuesday, September 1, 2026 at 14:00 BST",
    "location": "google_meet",
    "meetingUrl": "https://meet.google.com/abc-defg-hij"
  },
  "confirmationEmail": "A confirmation email will be sent to [email protected] if this event has email notifications configured."
}

meetingUrl is the Google Meet, Zoom or Teams link, whichever the event is configured for. It is null for in-person or phone meetings.

Errors

Errors return a JSON body with an error string, sometimes with extra context to help you recover.

Paid event types

Event types that collect payment cannot be booked through the API, because payment is taken during checkout on the booking page. Such a request returns 400 along with the bookingUrl — send the user there to finish. You can detect these ahead of time via requiresPayment on GET /event-types.