Events / API reference

Create an event

Start a draft event. Add tickets and publish when the details are ready.

POST/events

Authentication

Send your live API key in the Authorization: Bearer header. All requests use https://api.celerlinks.com/api-service.

Request parameters

titlestring · body · required

Event name, up to 255 characters.

descriptionstring · body · optional

Event description.

starts_atstring · body · optional

ISO 8601 start date/time, including timezone offset.

ends_atstring · body · optional

Must be on or after starts_at.

timezonestring · body · optional

IANA timezone, for example Africa/Lagos.

location_typestring · body · optional

physical, virtual, or hybrid.

venuestring · body · optional

Venue name.

addressstring · body · optional

Venue address.

citystring · body · optional

City name.

virtual_urlstring · body · optional

Meeting URL for virtual or hybrid events.

capacityinteger · body · optional

Maximum capacity, at least 1.

visibilitystring · body · optional

public, private, or unlisted.

require_approvalboolean · body · optional

Whether guests need approval.

Examples are illustrative. Catalogue IDs, product codes, prices, and provider-specific fields must come from your current API responses.

cURL request

curl --request POST 'https://api.celerlinks.com/api-service/events' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data '{
  "title": "Community meetup",
  "timezone": "Africa/Lagos",
  "location_type": "physical",
  "venue": "Your venue",
  "visibility": "public"
}'

Illustrative response

{
  "success": true,
  "message": "Request completed successfully",
  "data": {
    "id": 123,
    "title": "Community meetup",
    "status": "draft"
  }
}