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 Booking API

A booking of a resource in the booking calendar.

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

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

This API exposes 10 operations across 7 paths, and defines 36 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.

10 operations 7 paths 36 schemas 2 DELETE4 GET1 PATCH3 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 Booking 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 10

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

Booking 10

A booking of a resource in the booking calendar.

POST
/bookings
Book as admin
create-admin-booking body → 201202400
GET
/recurring_bookings/{recurringId}
List recurring
get-recurring-bookings 1 param → 200
DELETE
/recurring_bookings/{bookingId}/following
Delete following
delete-following-recurring-bookings 1 param → 202
POST
/bookings_preview
Bookings preview
post-bookings-preview body → 200
DELETE
/bookings/{id}
Delete booking
delete-space-booking 1 param → 204409
GET
/bookings/{id}
Single booking
get-booking 1 param → 200
PATCH
/bookings/{id}
Update booking
update-space-booking 1 param body → 200400409
GET
/memberships/{membershipId}/bookings
For membership/time
get-membership-bookings 3 params → 200
POST
/memberships/{membershipId}/bookings
Book as member
create-membership-booking 1 param body → 201400
GET
/spaces/{spaceId}/bookings
List space bookings
get-space-bookings 4 params → 200

Schemas 36

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

currency
string
ISO 4217 3 letter currency code.
relationship-linkage
object
1 property 1 required
links
object
-booking-preview-data
object
5 properties 4 required
recurrence-weekdays
Only when frequency is weekly: Allows to repeat a booking on multiple weekdays. 1 is Monday, 7 is Sunday.
related-link
object
1 property 1 required
money
object
1 property 1 required
create-bookings-preview
object
1 property 1 required
tax
object
3 properties
booking
object
2 properties 1 required
date
string
A date in the form YYYY-MM-DD.
booking-previews
object
4 properties 1 required
create-booking
object
1 property 1 required
error
object
8 properties
-booking-extra-data
object
6 properties 6 required
decimal
string
A decimal number.
recurring-bookings
object
4 properties 1 required
resource-discount
object
2 properties 2 required
pagination-links
object
5 properties 3 required
recurrence
object
1 property 1 required
link
A link MUST be represented as either: a string containing the link's URL or a link object.
recurrence-2
object
1 property 1 required
price
object
Price including net/gross value and all taxes.
4 properties 4 required
fixed-rate-count
object
3 properties 3 required
hours-minutes-object
object
2 properties 2 required
-booking-data
object
5 properties 2 required
linkage
object
The "type" and "id" of a linked entity.
2 properties 2 required
resource-paid-time-cap
object
1 property 1 required
update-booking
object
1 property 1 required
estimated-payable-price
object
Estimated price to be payable after any credits or discounts are applied upon invoicing for that item.
4 properties 4 required
optional-relationship-linkage
object
1 property 1 required
failure
object
4 properties 1 required
jsonapi
object
An object describing the server's implementation
2 properties
meta
object
Non-standard meta-information that can not be represented as an attribute or relationship.
bookings
object
4 properties 1 required
booking-extra

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cobot-booking-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 Credit API
Cobot Built-in Email Customizations API
Cobot Calendar Blocker API
Cobot Check In API
Cobot Contact API
Cobot Cost Center API
Cobot Customer API
Where this information came from

This is an independent, third-party profile of Cobot Booking 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.