canonical: https://jentic.com/apis/robinpowered.com/robinpowered

# Robinpowered Robin Workplace API

The Robin Workplace API provides programmatic access to manage workplaces, spaces, desks, events, reservations, and more. The API exposes 71 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get current authentication details, get an organization by id. Covers 71 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Get current authentication details
- Create a location for an organization
- List locations for an organization
- Query and filter Robin Workplace API records by parameters
- Monitor Robin Workplace API operational status and events

## Use cases

### E-Commerce Operations

Use the Robin Workplace API to perform e commerce operations programmatically. The API provides 71 endpoints covering core functionality including get current authentication details, get an organization by id, create a location for an organization.

Example prompt: Call GET /auth to get current authentication details

### Automated Auth Management

Automate auth operations by combining multiple Robin Workplace API endpoints. Agents can get an organization by id and then create a location for an organization in a single workflow.

Example prompt: Call GET `/organizations/{id}` to get an organization by id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Robin Workplace API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get current authentication details', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/auth` | Get current authentication details |
| GET | `/organizations/{id}` | Get an organization by ID |
| POST | `/organizations/{id}/locations` | Create a location for an organization |
| GET | `/organizations/{id}/locations` | List locations for an organization |
| POST | `/organizations/{id}/users` | Create a user for an organization |
| GET | `/organizations/{id}/users` | List users for an organization |
| GET | `/organizations/{id}/users/{userId}` | Get a specific user in an organization |
| POST | `/organizations/{id}/amenities` | Create an amenity for an organization |

## Key resources

- **Auth** — Authentication operations
- **Organizations** — Organization management
- **Users** — User management
- **Locations** — Location management
- **Spaces** — Space (room) management

## Why Jentic

- **Setup:** Wiring the Robin Workplace API by hand means formatting your apiKey as Access-Token in the Authorization header, sending it on every call to the api.robinpowered.com host, and threading organization ids through the locations, users, and amenities paths yourself. Through Jentic you install once, import the Robin Workplace API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Robin puts the resource id in the URL path (`/organizations/{id}/users/{userId}`), so a rule can pin your agent to one organization and its users, locations, and amenities. You choose the operations it may call, so writes like creating a user or location are not included unless you add them.
- **Credential handling:** Your Robin API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list users in an organization' or 'create a location', and Jentic returns the matching Robin Workplace API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Robin Workplace API use?

The Robin Workplace API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get current authentication details with the Robin Workplace API?

Yes. Use the GET /auth endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Robin Workplace API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get current authentication details through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get current authentication details'. Jentic returns the matching Robin Workplace API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Robin Workplace API have?

The Robin Workplace API exposes 71 endpoints covering auth, organizations, users operations.

### Can I limit what my agent is allowed to do with the Robin Workplace API?

Yes. Because you run Jentic One yourself, your own rules decide which Robin Workplace API operations and which stored API key the agent may use. Since Robin puts the resource id in the URL path, such as `/organizations/{id}/users/{userId}`, you can pin the agent to a single organization and its users, locations, and amenities. You also choose the operations it may call, so writes like creating a user or a location stay off limits unless you add them.