Cobot API

Name: Cobot 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.

Install Jentic One Beta

Connect the Cobot API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cobot API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcobot.me%2Fcobot" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcobot.me%2Fcobot" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Cobot 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}

GET STARTED

Start building with Cobot API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cobot 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 Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Cobot by hand means running its OAuth 2.0 authorization-code flow, tracking scopes and token refresh, targeting www.cobot.me/api, and handling retries yourself. Through Jentic you install once, import the Cobot API from the API Directory, store the access token once, and your agent calls it.

Permission scoping

Cobot puts the membership id in the URL path (/memberships/{membershipId}/...), so a rule can pin your agent to one membership, and its OAuth scopes (read, write, read_memberships, write_memberships) bound what the token can touch. You choose the operations it may call, so ones like cancelling a membership are not included unless you add them.

Credential isolation

Your Cobot OAuth access token is stored once, encrypted, by your own Jentic One instance and added to the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'cancel a coworking membership' or 'list members', and Jentic returns the matching Cobot operation with its parameter schema so the agent calls the right endpoint without browsing the api-docs site.

FAQs

Specific to using Cobot 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Cobot API?

Yes. Because you run Jentic One yourself, your own rules decide which Cobot operations and credentials the agent may use, so you can grant read-only endpoints like GET /memberships while withholding write actions such as POST /memberships/{membershipId}/cancellation unless you explicitly add them. Since Cobot puts the membership id in the URL path, a rule can pin the agent to a single membership, and the OAuth scopes you store (read, write, read_memberships, write_memberships) bound what its token can touch. The agent can only call the operations and scopes you have permitted.

Cobot API

Connect the Cobot API to your agent

Capabilities

Start building with Cobot API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs