How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cobot Event API

Spaces can run events for their members or the public.Events are created and later published by admins, at which point members are able to see and attend them.Admins can also create messages for events, which are sent to attendees based on triggers such as someone havingjust attended an event.

Cobot Event API is one of 44 APIs that Cobot publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 18 operations across 12 paths, and defines 54 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.cobot.me.

18 operations 12 paths 54 schemas 4 DELETE7 GET2 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.cobot.me
Authentication
OpenID Connect, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

Cobot Event API declares 2 security schemes for authenticating requests. It supports OpenID Connect (OpenId) discovered at https://www.cobot.me/.well-known/openid-configuration. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 58 scopes. By default, every request must be authenticated.

  • OAuth2 — OAuth is "an open protocol to allow secure API authorization in a simple and standard method from desktop and web applications.". "OAuth 2.0 is the next evolut…

Paths & Operations 18

Across 12 paths, the API surfaces 18 operations — 4 DELETE, 7 GET, 2 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Event 18

Spaces can run events for their members or the public. Events are created and later published by admins, at which point members are able to see and attend them. Admins can also cr…

POST
/events
Create event
create-admin-event body → 201
GET
/events/{id}
Single event
get-event 2 params → 200
PATCH
/events/{id}
Update event
update-event 1 param body → 200
DELETE
/events/{id}
Delete event
delete-event 1 param → 204
POST
/event_attendances
Attend event
attend-event body → 201409
GET
/event_attendances/{id}
Single event attendance
get-event-attendance 2 params → 200
DELETE
/event_attendances/{id}
Unattend event
unattend-event 1 param → 204409
GET
/events/{id}/attendances
List attendances
list-event-attendances 2 params → 200
POST
/event_messages
Create message
create-event-messages body → 201
GET
/event_messages/{id}
Single message
get-event-message 1 param → 200
PATCH
/event_messages/{id}
Update message
update-event-message 1 param body → 200
DELETE
/event_messages/{id}
Delete message
delete-event-message 1 param → 204
GET
/events/{id}/messages
List messages
get-event-event-messages 1 param → 200
POST
/events/{id}/publication
Publish as admin
publish-admin-event 1 param → 201409
DELETE
/events/{id}/publication
Depublish as admin
depublish-admin-event 1 param → 200409
POST
/event_ticket_purchases
Create an event ticket purchase
create-event-ticket-purchase body → 201422
GET
/spaces/{spaceId}/events
List events
list-events 9 params → 200
GET
/spaces/{spaceId}/events/tags
List Tags
list-event-tags 3 params → 200

Schemas 54

The contract defines 54 schemas that model the data the API accepts and returns. The most detailed are invoiceAddress (10 properties), error (8 properties), structuredAddress (7 properties), pagination-links (5 properties). Each schema is shown below with its type and property counts.

event
object
2 properties 1 required
event-message
object
1 property 1 required
image-upload
object
1 property 1 required
currency
string
ISO 4217 3 letter currency code.
relationship-linkage
object
1 property 1 required
links
object
related-link
object
1 property 1 required
event-tags
object
1 property 1 required
-contact-data
object
4 properties 2 required
create-event-attendance
object
1 property 1 required
-event-message-data
object
4 properties 4 required
event-attendances
object
4 properties 1 required
tax
object
3 properties
structuredAddress
object
Either name or company is required.
7 properties 6 required
relationship-linkage-array
object
1 property 1 required
failure
object
4 properties 1 required
-membership-data
object
4 properties 2 required
date
string
A date in the form YYYY-MM-DD.
event-message-trigger
string
What triggers the message to be sent. The 'published' trigger will send a message to all members when an event is published. If no published message is created…
error
object
8 properties
revenue-account
object
2 properties 2 required
event-messages
object
3 properties 1 required
decimal
string
A decimal number.
photo
object
3 properties
pagination-links
object
5 properties 3 required
event-attendance
object
2 properties 1 required
color
string
Color hex code, e.g. FF0000
address-2
object
Either name or company is required.
3 properties 3 required
link
A link MUST be represented as either: a string containing the link's URL or a link object.
price
object
Price including net/gross value and all taxes.
4 properties 4 required
avatar-photo
object
5 properties
update-event
object
1 property 1 required
gross-amount-with-currency
object
2 properties 2 required
event-resources
object
The booking calendar resources to be booked for the event.
1 property 1 required
pagination-meta
object
2 properties
cost-center
object
2 properties 2 required
linkage
object
The "type" and "id" of a linked entity.
2 properties 2 required
event-message-body
string
A custom, plain-text message added to the auto-generated email.
invoiceAddress
object
10 properties 8 required
optional-relationship-linkage
object
1 property 1 required
-event-attendance-data
object
4 properties 4 required
address
object
3 properties
-event-ticket-purchase-data
object
4 properties 4 required
net-amount-with-currency
object
2 properties 2 required
email
string
event-ticket-purchase
object
1 property 1 required
update-event-message
object
1 property 1 required
create-event-ticket-purchase
object
1 property 1 required
create-event-message
object
1 property 1 required
events
object
4 properties 1 required
create-event
object
1 property 1 required
meta
object
Non-standard meta-information that can not be represented as an attribute or relationship.
jsonapi
object
An object describing the server's implementation
2 properties
-event-data
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cobot-event-api-openapi.yml Raw ↑

Other APIs Cobot publishes across the network.

Cobot API v1 (legacy)
Cobot MCP Server
Cobot Allocation API
Cobot Approval API
Cobot Article API
Cobot Booking API
Cobot Booking Credit API
Cobot Built-in Email Customizations API
Cobot Calendar Blocker API
Cobot Check In API
Cobot Contact API
Cobot Cost Center API
Where this information came from

This is an independent, third-party profile of Cobot Event API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.