canonical: https://jentic.com/apis/dev.cobot.me/cobot # Dev Cobot Cobot API Jentic publishes the only available OpenAPI specification for Cobot API, keeping it validated and agent-ready. Cobot is coworking management software used to run shared workspaces - handling member sign-ups, billing plans, bookings, and access. The REST API exposes spaces, memberships, and membership lifecycle operations including cancellations and confirmations, so operators can sync members with their CRM, automate onboarding, and report on cancellation activity without working in the Cobot dashboard. ## For AI agents Manage coworking spaces and memberships in Cobot - create memberships, confirm sign-ups, handle cancellations, and pull space data through OAuth-authenticated calls. ## Scope Does not handle door access control hardware, accounting ledgers, or payment processing - use for coworking memberships, space configuration, and cancellations only. ## Capabilities - List and update space details for a given subdomain - Create new memberships and update member contact information - Confirm a pending membership sign-up to activate the member - Process membership cancellations and pull cancellation lists for reporting - Retrieve the space logo for use in branded portals - Delete or close out a membership when a member leaves the space - Sync space member data into a CRM or accounting tool ## Use cases ### Member Sign-Up to CRM Sync Coworking operators sync new Cobot memberships into their CRM so sales and customer success teams have a single source of truth. POST /memberships creates the member in Cobot, while a follow-on poll of GET /memberships against the CRM keeps records in sync. This avoids double data entry as new members onboard. Example prompt: POST /memberships with a new member's email and plan, then push the returned membership ID into the CRM as the canonical reference. ### Cancellation Reporting and Win-Back Customer success teams pull POST and GET data on cancellations through /memberships/{id}/cancellation and /memberships/cancellations to track churn drivers. Patterns in cancellations feed win-back campaigns and pricing reviews. Example prompt: Call GET /memberships/cancellations, group results by reason, and create a weekly churn report for the operations team. ### Front Desk Confirmation Flow Front desk and community managers confirm pending member sign-ups via POST /memberships/{id}/confirmation. This is the gate between a self-serve form fill and an active billing record, so handing it to a kiosk app or automation rule speeds up morning queues. Example prompt: POST /memberships/{id}/confirmation for each pending membership in the morning queue to activate them in bulk. ### Space Configuration Sync Multi-location operators keep space details consistent across systems via GET and PUT on /spaces/{subdomain}. This drives the right address and branding into invoices, badges, and partner portals when a space updates its name or relocates. Example prompt: PUT /spaces/{subdomain} with updated address details, then refresh the partner portal cache to pick up the changes. ### Agent-Driven Coworking Operations AI agents help community managers triage sign-ups, confirm members, and handle cancellations through Jentic. Cobot's OAuth tokens stay in your Jentic One instance so the agent can resolve intents like 'confirm all pending sign-ups from this morning' without holding credentials. Example prompt: Search Jentic for 'confirm a Cobot membership', load the POST /memberships/{id}/confirmation operation, and execute it for each pending member. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /spaces | Create a coworking space | | PUT | /spaces/{subdomain} | Update space details | | GET | /spaces/{subdomain}/logo | Retrieve a space's logo | | POST | /memberships | Create a new membership | | PUT | /memberships/{id} | Update a membership | | POST | /memberships/{id}/cancellation | Cancel a membership | | POST | /memberships/{id}/confirmation | Confirm a pending membership | | GET | /memberships/cancellations | List membership cancellations | ## Key resources - **Spaces** — Manage coworking space details and branding - **Memberships** — Create, update, confirm, and cancel memberships ## Why Jentic - **Setup:** Wiring the Cobot API by hand means completing its OAuth 2.0 flow, resolving the per-space subdomain host (https://{subdomain}.cobot.me/api), and building the space and membership calls yourself. Through Jentic you install once, import the Cobot API from the API Directory, connect the account once, and your agent calls it. - **Permission scoping:** Cobot puts the space subdomain and membership id in the URL path (/spaces/{subdomain}, /memberships/{id}), so a rule can pin your agent to one space: it can confirm memberships and read cancellations there and nothing else. You choose the operations it may call, so a membership cancellation is not included unless you add that operation. - **Credential handling:** Your Cobot OAuth token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'confirm a Cobot membership' or 'list cancellations', and Jentic returns the matching Cobot operation with its input schema so the agent calls the right endpoint without reading the docs. ## Related APIs - **Calendly API** — Calendly handles meeting scheduling for coworking community managers alongside Cobot's membership flow. - **Stripe API** — Stripe handles billing for coworking plans alongside Cobot's membership records. - **HubSpot CRM Contacts API** — Sync Cobot members into HubSpot CRM as contacts for sales and lifecycle automation. ## FAQ ### Why is there no official OpenAPI spec for Cobot API? Cobot does not publish an OpenAPI specification. 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? Cobot uses OAuth 2.0. Public endpoints require no auth; private endpoints require an OAuth2 access token with the appropriate scope. Through Jentic the access token is stored encrypted in the vault and injected at call time. ### Can I create memberships with the Cobot API? Yes - POST /memberships creates a new member tied to a space. Follow up with POST /memberships/{id}/confirmation to activate the member once the sign-up is verified. ### How do I track cancellations with the Cobot API? Use POST /memberships/{id}/cancellation to record a cancellation and GET /memberships/cancellations to list cancellations across the space for churn reporting. ### What are the rate limits for the Cobot API? Cobot enforces around 60 requests per minute per user on most endpoints, though some endpoints differ. Implement exponential backoff on 429 responses for batch syncs. ### How do I confirm a membership through Jentic? Search Jentic for 'confirm a Cobot membership', load the POST /memberships/{id}/confirmation operation, and execute it with the membership ID. Jentic injects the OAuth token at execution time. ### Can I limit what my agent is allowed to do with the Cobot API? Yes. Because your Jentic One instance is self-hosted, you decide which Cobot operations the agent may call and which OAuth credentials it uses, so it only touches what your own rules permit. Since Cobot puts the space subdomain and membership ID in the URL path (/spaces/{subdomain}, /memberships/{id}), you can pin the agent to a single space and let it confirm sign-ups via POST /memberships/{id}/confirmation and read churn via GET /memberships/cancellations while excluding everything else. A destructive operation like POST /memberships/{id}/cancellation is not available to the agent unless you explicitly add it.