Realwork Labs Stoplight Realwork API

Name: Realwork API
Brand: Realwork API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationbearer9 EndpointsREST

For Agents

Programmatically list workspaces, get workspace. Covers 9 operations with bearer authentication.

Install Jentic One Beta

Connect the Realwork API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Realwork 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 Realwork API.

List Workspaces

Get Workspace

Create Project

Access Realwork API productivity resources via REST API

GET STARTED

Start building with Realwork API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Realwork API for, with concrete tasks.

★ Productivity Operations

Use the Realwork API to perform productivity operations programmatically. The API provides 9 endpoints covering core functionality including list workspaces, get workspace, create project.

Call GET /workspaces to list workspaces

Automated projects Management

Automate projects operations by combining multiple Realwork API endpoints. Agents can get workspace and then create project in a single workflow.

Call GET /workspaces/{id} to get workspace, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Realwork 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 bearer tokens manually.

Search Jentic for 'list workspaces', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — work management and collaboration api (stoplight documentation not accessible).

METHOD

PATH

DESCRIPTION

GET

/workspaces

List Workspaces

GET

/workspaces/{id}

Get Workspace

POST

/projects

Create Project

GET

/projects

List Projects

GET

/projects/{id}

Get Project

POST

/tasks

Create Task

GET

/tasks

List Tasks

GET

/tasks/{id}

Get Task

GET

/workspaces

List Workspaces

GET

/workspaces/{id}

Get Workspace

POST

/projects

Create Project

GET

/projects

List Projects

GET

/projects/{id}

Get Project

POST

/tasks

Create Task

Why Jentic?

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

Credential isolation

Realwork API bearer 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 workspaces') and Jentic returns the matching Realwork API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Realwork API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Realwork API through Jentic.

What authentication does the Realwork API use?

The Realwork API uses a Bearer token in the Authorization header. 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 workspaces with the Realwork API?

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

What are the rate limits for the Realwork 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 workspaces through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list workspaces'. Jentic returns the matching Realwork API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Realwork API have?

The Realwork API exposes 9 endpoints covering projects, tasks, workspaces operations.

Realwork Labs Stoplight Realwork API

Connect the Realwork API to your agent

Capabilities

Start building with Realwork API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs