Robotstudio ABB Robot Web Services API
✓ Official Vendor SpecPaymentsBilling Subscriptionsbasic126 EndpointsREST
For Agents
Programmatically list all controller resources, retrieve environment variable value. Covers 126 operations with basic authentication.
Use for: I need to all controller resources, I want to environment variable value, Search for set controller language, Find all restart controller
Not supported: Does not handle communications, crm, or developer tools — use for payments only.
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.
Install Jentic One Beta
Connect the ABB Robot Web Services API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ABB Robot Web Services 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 ABB Robot Web Services API.
List all controller resources
Retrieve environment variable value
Set controller language
Restart controller
Get warm restart count since last I-start
Use Cases
Patterns agents use ABB Robot Web Services API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'list all controller resources', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
126 endpoints — restful api for interacting with abb robot controllers.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
ABB Robot Web Services API basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'list all controller resources') and Jentic returns the matching ABB Robot Web Services API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct ABB Robot Web Services API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using ABB Robot Web Services API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED