Robotstudio ABB Robot Web Services API

Name: ABB Robot Web Services API
Brand: ABB Robot Web Services API
Availability: InStock

✓ Official Vendor SpecPaymentsBilling Subscriptionsbasic126 EndpointsREST

For Agents

Programmatically list all controller resources, retrieve environment variable value. Covers 126 operations 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.

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 | sh

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 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 ABB Robot Web Services API.

List all controller resources

Retrieve environment variable value

Set controller language

Restart controller

GET STARTED

Start building with ABB Robot Web Services API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

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 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.

Robotstudio ABB Robot Web Services API

Connect the ABB Robot Web Services API to your agent

Capabilities

Start building with ABB Robot Web Services API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs