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

# RAIDLOG API

RESTful API for managing RAIDLOG workspaces, projects, risks, actions, issues, decisions, and more. The API exposes 28 endpoints secured with bearer authentication.

## For AI agents

Programmatically login, logout. Covers 28 operations with bearer authentication.

## Scope

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

## Capabilities

- Login
- Logout
- Get user profile
- Replace user profile
- Partial update user profile
- List workspaces

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'login', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Users** — User authentication and profile management
- **Workspaces** — Workspace management
- **Tenants** — Tenant management
- **Projects** — Project management
- **Risks** — Risk management

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 66 / 100
- **View full report:** https://jentic.com/apis/raidlog.com/raidlog/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the RAIDLOG API by hand means learning its bearer auth, choosing between the api.us.raidlog.com and api.eu.raidlog.com hosts, and handling retries across its user and workspace operations yourself. Through Jentic you install once, import RAIDLOG from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** RAIDLOG puts the workspace uuid in the URL path (`/workspaces/{uuid}`), so a rule can pin your agent to one workspace: it reads and updates that workspace and nothing else. You choose the operations it may call, so a write like updating users is not included unless you add it.
- **Credential handling:** Your RAIDLOG token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a workspace by id' or 'list workspaces', and Jentic returns the matching RAIDLOG operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the RAIDLOG API?

Yes. Jentic One is self-hosted, so your own rules decide which RAIDLOG operations and credentials the agent may use. Because RAIDLOG carries the workspace uuid in the URL path (`/workspaces/{uuid}`), you can pin the agent to a single workspace so it reads and updates that one and nothing else. You also choose the exact operations it may call, so a write such as replacing a user profile via PUT /users stays out of reach unless you explicitly allow it.