Cobot API

Name: Cobot API API
Brand: Cobot API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact Managementoauth220 EndpointsREST

For Agents

Manage coworking spaces and memberships on Cobot — create spaces, onboard members, confirm or cancel memberships, and read member profiles.

Quickstart

Get started with Cobot API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list Cobot coworking memberships"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cobot API API.

Create and update coworking spaces via POST /spaces and PUT /spaces/{subdomain}

List and inspect memberships across a space via GET /memberships and GET /memberships/{membershipId}

Create, update and delete admin-managed memberships through POST /memberships and DELETE /memberships/{membershipId}

Cancel or restore a membership using POST /memberships/{membershipId}/cancellation and the matching DELETE

GET STARTED

Start building with Cobot API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Cobot API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Cobot API, keeping it validated and agent-ready. The API powers the Cobot coworking-space management platform — creating and updating spaces, managing member memberships and cancellations, connecting users to memberships, and reading member pictures and space logos. Authentication is OAuth 2.0 authorization code with read, write, read_memberships, and write_memberships scopes, so integrators can grant exactly the access they need on a per-space basis.

Use Cases

Patterns agents use Cobot API API for, with concrete tasks.

★ Member Onboarding Automation

Create memberships from an external signup form and confirm them once payment clears. POST /memberships creates the record as admin, POST /memberships/{membershipId}/confirmation moves it to active, and POST /memberships/{membershipId}/user links the new user account. Replacing the manual flow with this sequence cuts onboarding to under a minute per member.

Create a membership via POST /memberships, then confirm it with POST /memberships/{membershipId}/confirmation and connect user id 99 via POST /memberships/{membershipId}/user.

Cancellation and Churn Reporting

Track churn at a coworking space by reading canceled memberships and surfacing trends in a BI tool. GET /memberships/cancellations returns the canceled set and POST /memberships/{membershipId}/cancellation lets the workflow act on a request, while DELETE on the same path can undo a cancellation if a member changes their mind. Useful for monthly churn dashboards.

Call GET /memberships/cancellations and return the list of memberships canceled in the previous month with their cancellation date.

Multi-Space Administration

Manage several coworking locations from a single dashboard. POST /spaces creates a new location, GET /spaces/{subdomain} reads its current configuration, and PUT /spaces/{subdomain} pushes config changes such as opening hours or branding. The OAuth 2.0 scopes let an integrator give a regional manager write on their own space and read-only across the rest.

Update the space at subdomain 'london-bridge' via PUT /spaces/london-bridge to change the displayed timezone.

AI Agent Coworking Workflows via Jentic

An AI assistant for a coworking operator uses Jentic to handle inbound member requests — onboarding, cancellation, profile updates — without holding the OAuth tokens. The agent searches for 'cancel a Cobot membership', loads the schema, and executes. Jentic injects the access token at execution time and respects the granted scopes.

Use Jentic to search for 'cancel a Cobot membership', load the POST /memberships/{membershipId}/cancellation schema, and cancel membership id 12345 effective end of month.

Key Endpoints

20 endpoints — jentic publishes the only available openapi specification for cobot api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/spaces

Create a coworking space

GET

/memberships

List members of a space

POST

/memberships

Create an admin-managed membership

POST

/memberships/{membershipId}/cancellation

Cancel a membership

POST

/memberships/{membershipId}/confirmation

Confirm a pending membership

POST

/memberships/{membershipId}/user

Connect a user account to a membership

GET

/memberships/cancellations

List canceled memberships

POST

/spaces

Create a coworking space

GET

/memberships

List members of a space

POST

/memberships

Create an admin-managed membership

POST

/memberships/{membershipId}/cancellation

Cancel a membership

POST

/memberships/{membershipId}/confirmation

Confirm a pending membership

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

OAuth 2.0 access tokens are stored encrypted in the Jentic vault and added to the Authorization header at execution time. Agents call Cobot operations within the granted scopes (read, write, read_memberships, write_memberships) without ever receiving the raw token.

Intent-based discovery

Agents search by intent (e.g. 'cancel a coworking membership' or 'list members') and Jentic returns the matching Cobot operation with its parameter schema, so the agent can act on the right endpoint without browsing the api-docs site.

Time to first call

Direct Cobot integration: one to two days for OAuth setup, scope handling, and the membership lifecycle endpoints. Through Jentic: under one hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Calendly

Calendly handles meeting and tour scheduling for coworking sales teams.

Use Calendly to book space tours; use Cobot to convert the booked tour into a confirmed membership.

Complementary

Stripe

Stripe handles subscription billing for the underlying membership plan.

Use Stripe to charge the membership and Cobot to provision and cancel space access on the back of subscription state.

Complementary

HubSpot

HubSpot serves as the CRM where leads are captured before they become Cobot members.

Use HubSpot for top-of-funnel lead tracking and Cobot for the activated member record once they sign up.

FAQs

Specific to using Cobot API API through Jentic.

Why is there no official OpenAPI spec for Cobot API?

Cobot does not publish an OpenAPI specification on its developer site. Jentic generates and maintains this spec so that AI agents and developers can call Cobot API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Cobot API use?

The API uses OAuth 2.0 authorization code with scopes read, write, read_memberships, and write_memberships. The authorization endpoint is https://www.cobot.me/oauth/authorize and tokens are exchanged at https://www.cobot.me/oauth/access_token. Through Jentic the access token is stored encrypted in the vault and added to requests at execution time.

Can I cancel a member's membership through the Cobot API?

Yes. POST /memberships/{membershipId}/cancellation cancels a membership, and DELETE on the same path undoes the cancellation if the member changes their mind. Use GET /memberships/cancellations to list everyone canceled in the period for reporting.

What are the rate limits for the Cobot API?

The OpenAPI spec does not declare numeric rate limits. Cobot applies tenant-level throttling, so integrations that poll /memberships frequently should switch to event-driven reads or back off on 429 responses.

How do I onboard a new member through Jentic?

Search Jentic for 'create a Cobot membership', load the POST /memberships schema, and execute with the member detail. Then load POST /memberships/{membershipId}/confirmation to activate it. Install the SDK with pip install jentic and call it via the async client.

Does the Cobot API support self-service for individual members?

Yes. The /membership endpoints (without an id) operate on the authenticated user's own membership — GET to read, POST to create, PUT to update, and DELETE to cancel — separate from the admin /memberships/{membershipId} surface.