1:Many Integration API Guide

This API supports the following core functions:

  • Capturing customer leads

  • Retrieving available conference slots

  • Registering a user for an event

  • Canceling (unregistering) a user’s event registration

All requests must be authenticated using API headers.


Base URL

https://widget01.popin.to

Authentication

All API requests require the following headers:

X-API-KEY: your-api-key  
X-TOKEN: seller-id

If the API key is missing or invalid, the API responds with:

401 — Unauthorized


Endpoints Overview

All endpoints below are consistent across vendors.


1. Capture Customer Lead

POST /api/v1/external/conference/capture

Used to add a new customer lead into the system.

Request Body

Success Response — 200

Error Responses

  • 401 Unauthorized

  • 422 Validation Error


2. Get Available Conference Slots

GET /api/v1/external/conference/slots

Used to fetch available conference events for a customer.

Two Usage Modes

A. Customer-specific slots (pass user_id)

Example:

This returns slots relevant to the specified user, including registered events.

B. General slots (no user_id required)

If you need a general event-slots link that can be shared with any customer, you can call the same endpoint without passing user_id.

Example:

This returns generic available slots that are not user-specific.


Success Response — 200

Error Responses

  • 401 Unauthorized

  • 422 Validation Error


3. Register User for Event

POST /api/v1/external/conference/register

Registers a customer for a selected event.

Request Body

Success Response — 200

Error Responses

  • 401 Unauthorized

  • 422 Validation Error


4. Cancel User Event Registration

POST /api/v1/external/conference/cancel

Cancels a user's registration from an event.

Request Body

Success Response — 200

Error Responses

  • 401 Unauthorized

  • 422 Validation Error


Data Models

CaptureRequest

CaptureResponse

SlotsResponse

RegisterRequest

RegisterResponse

ValidationError

Last updated