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

# Robotstudio ABB Robot Web Services API

RESTful API for interacting with ABB robot controllers. Provides access to controller configuration, I/O systems, RAPID programs, file management, event logging, mastership control, panel operations, subscriptions, system information, and user management. The API exposes 126 endpoints secured with basic authentication.

## For AI agents

Programmatically list all controller resources, retrieve environment variable value. Covers 126 operations with basic authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- List all controller resources
- Retrieve environment variable value
- Set controller language
- Restart controller
- Get warm restart count since last I-start

## Use cases

### Payments Operations

Use the ABB Robot Web Services API to perform payments operations programmatically. The API provides 126 endpoints covering core functionality including list all controller resources, retrieve environment variable value, set controller language.

Example prompt: Call GET /ctrl to list all controller resources

### Automated Controller Management

Automate controller operations by combining multiple ABB Robot Web Services API endpoints. Agents can retrieve environment variable value and then set controller language in a single workflow.

Example prompt: Call GET /ctrl/{envName} to retrieve environment variable value, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call ABB Robot Web Services 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 basic tokens manually.

Example prompt: Search Jentic for 'list all controller resources', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /ctrl | List all controller resources |
| GET | /ctrl/{envName} | Retrieve environment variable value |
| POST | /ctrl/lang | Set controller language |
| POST | /ctrl/restart | Restart controller |
| GET | /ctrl/restart/restartcount | Get warm restart count since last I-start |
| GET | /ctrl/clock | Get system time |
| PUT | /ctrl/clock | Set system time |
| POST | /ctrl/clock/timezone | Set timezone |

## Key resources

- **Controller** — Controller service operations
- **IO** — I/O system management
- **RAPID** — RAPID program execution and modules
- **FileService** — File system operations
- **Elog** — Event log management

## Why Jentic

- **Setup:** Wiring the ABB Robot Web Services API by hand means implementing its HTTP basic auth, pointing at the controller on its local host (127.0.0.1 or the 192.168.125.1 LAN address), and handling the request plumbing yourself. Through Jentic you install once, import the ABB Robot Web Services API from the API Directory, store the basic credentials once, and your agent calls it.
- **Permission scoping:** This spec puts the controller resource in the URL path (/ctrl/{envName}), so a rule can pin your agent to the controller reads it needs. You choose the operations it may call, so state-changing ones like restarting the controller or setting the clock timezone are not included unless you add them.
- **Credential handling:** Your ABB Robot Web Services basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list controller resources' or 'read the controller clock', and Jentic returns the matching ABB Robot Web Services operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the ABB Robot Web Services API use?

The ABB Robot Web Services API uses HTTP Basic authentication with username and password. 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 list all controller resources with the ABB Robot Web Services API?

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

### What are the rate limits for the ABB Robot Web Services 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 list all controller resources through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list all controller resources'. Jentic returns the matching ABB Robot Web Services API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the ABB Robot Web Services API have?

The ABB Robot Web Services API exposes 126 endpoints covering controller, io, rapid operations.

### Can I limit what my agent is allowed to do with the ABB Robot Web Services API?

Yes. Because you run Jentic One yourself, your own rules decide which of the 126 operations and which basic credentials your agent may use. Since this API puts the controller resource in the URL path, such as GET /ctrl/{envName}, you can pin the agent to just the controller reads it needs and leave out state-changing calls like restarting the controller (POST /ctrl/restart) or setting the clock timezone (POST /ctrl/clock/timezone). Those operations run only if you explicitly allow them.