Skip to main content
This guide shows you how to create a fully functional platform user and verify they’re ready for bookings—in just two API calls.

​
Prerequisites

  • An Enterprise plan with API access enabled
  • Admin access to your meetergo account

​
Step 1: Create an API Key

1

Open API Keys

Go to my.meetergo.com/admin/api-keys.
2

Create key

Click Create API Key, optionally enter a name, and set the expiration (1-90 days).
3

Copy and save

Copy the key immediately and store it securely. It looks like:
ak_live:01234567-89ab-cdef-1234-567890abcdef:secretpart123
The key is only shown once. Store it in a password manager or environment variable. Keys have a mandatory expiration date and must be rotated to prevent service interruptions.

​
Step 2: Verify Your API Key

Use this call to validate your API Key and retrieve your authenticated user information: 
curl -X GET "https://api.meetergo.com/v4/user/me" \
  -H "Authorization: Bearer YOUR_API_KEY"
A successful response (200 OK) returns your full user object.

​
Step 3: Create a Platform User

This single endpoint creates a complete platform user with default availability and meeting type, making them immediately ready for bookings.

​
Basic Request

curl -X POST "https://api.meetergo.com/v4/user" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "[email protected]",
    "givenName": "John",
    "familyName": "Smith",
    "timezone": "Europe/London"
  }'

​
With Custom Availability & Meeting Type

{
  "email": "[email protected]",
  "givenName": "John",
  "familyName": "Smith",
  "timezone": "Europe/London",
  "availability": {
    "name": "John's Business Hours",
    "timezone": "Europe/London",
    "schedule": [
      {
        "dayOfWeek": "monday",
        "intervals": [{ "from": "09:00", "to": "17:00" }]
      },
      {
        "dayOfWeek": "tuesday",
        "intervals": [{ "from": "09:00", "to": "17:00" }]
      },
      {
        "dayOfWeek": "wednesday",
        "intervals": [{ "from": "09:00", "to": "17:00" }]
      },
      {
        "dayOfWeek": "thursday",
        "intervals": [{ "from": "09:00", "to": "17:00" }]
      },
      {
        "dayOfWeek": "friday",
        "intervals": [{ "from": "09:00", "to": "17:00" }]
      }
    ]
  },
  "meetingType": {
    "name": "45 Minute Discovery Call",
    "duration": 45,
    "slug": "john-smith-45min"
  }
}

​
Response (201 Created)

{
  "userId": "550e8400-e29b-41d4-a716-446655440000",
  "availabilityId": "660e8400-e29b-41d4-a716-446655440001",
  "meetingTypeId": "770e8400-e29b-41d4-a716-446655440002",
  "bookingUrl": "https://cal.meetergo.com/john-smith/45min-discovery-call",
  "companyId": "880e8400-e29b-41d4-a716-446655440003"
}
User Ready! The user is now fully configured and ready for bookings. The bookingUrl can be shared immediately with customers.
What was created automatically:
  • Platform user with the provided details
  • Default availability schedule (Mon-Fri 9-17 if not specified)
  • Default meeting type (30min Meeting if not specified)
  • Public booking URL for immediate use

​
Step 4: Verify Configuration

Query for open time slots to confirm the user is configured correctly and ready for bookings. 
curl -X GET "https://api.meetergo.com/v4/user/550e8400-e29b-41d4-a716-446655440000/bookable-windows?startDate=2024-01-15&endDate=2024-01-20" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "x-meetergo-api-user-id: 550e8400-e29b-41d4-a716-446655440000"

​
Response (200 OK)

A list of available start times in ISO 8601 format: 
{
  "windows": [
    "2024-01-15T09:00:00Z",
    "2024-01-15T09:45:00Z",
    "2024-01-15T10:30:00Z",
    "2024-01-15T11:15:00Z"
  ]
}
The user is now configured and available for booking!

​
What’s Next

Authentication

Learn about API key management and security

Users

Full user documentation

Availability

Customize availability schedules

Meeting Types

Create and manage meeting types

​
Common Issues

  • Check your API key is correct and complete
  • Ensure the key hasn’t expired
  • Verify the key is active (not deactivated)
Most endpoints require this header. Use the userId returned from user creation or get your own user ID from /v4/user/me.
  • Check the date range is in the future
  • Verify the user has availability configured
  • Ensure the user’s calendar isn’t fully booked
Timezones must be valid IANA timezone identifiers (e.g., Europe/London, America/New_York, Asia/Tokyo).