RAIDLOG API
✓ Official Vendor SpecProductivityCollaborationbearer28 EndpointsREST
For Agents
Programmatically login, logout. Covers 28 operations with bearer authentication.
Use for: I need to login, I want to logout, Search for user profile, Find all replace user profile
Not supported: Does not handle payments, communications, or crm — use for productivity only.
RESTful API for managing RAIDLOG workspaces, projects, risks, actions, issues, decisions, and more. The API exposes 28 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the RAIDLOG API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RAIDLOG 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 RAIDLOG API.
Login
Logout
Get user profile
Replace user profile
Partial update user profile
List workspaces
Use Cases
Patterns agents use RAIDLOG API for, with concrete tasks.
★ Productivity Operations
Use the RAIDLOG API to perform productivity operations programmatically. The API provides 28 endpoints covering core functionality including login, logout, get user profile.
Call POST /users/login to login
Automated Users Management
Automate users operations by combining multiple RAIDLOG API endpoints. Agents can logout and then get user profile in a single workflow.
Call POST /users/logout to logout, then verify the result
AI Agent Integration via Jentic
AI agents discover and call RAIDLOG 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 'login', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
28 endpoints — restful api for managing raidlog workspaces, projects, risks, actions, issues, decisions, and more.
METHOD
PATH
DESCRIPTION
POST
/users/login
Login
POST
/users/logout
Logout
GET
/users
Get user profile
PUT
/users
Replace user profile
PATCH
/users
Partial update user profile
GET
/workspaces
List workspaces
GET
/workspaces/{uuid}
Get workspace by ID
PUT
/workspaces/{uuid}
Update workspace
POST
/users/login
Login
POST
/users/logout
Logout
GET
/users
Get user profile
PUT
/users
Replace user profile
PATCH
/users
Partial update user profile
GET
/workspaces
List workspaces
GET
/workspaces/{uuid}
Get workspace by ID
PUT
/workspaces/{uuid}
Update workspace
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
RAIDLOG 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., 'login') and Jentic returns the matching RAIDLOG API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct RAIDLOG 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.
FAQs
Specific to using RAIDLOG API through Jentic.
What authentication does the RAIDLOG API use?
The RAIDLOG 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 login with the RAIDLOG API?
Yes. Use the POST /users/login endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the RAIDLOG 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 login through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'login'. Jentic returns the matching RAIDLOG API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the RAIDLOG API have?
The RAIDLOG API exposes 28 endpoints covering users, workspaces, tenants operations.
GET STARTED