canonical: https://jentic.com/apis/sydnee.app/sydnee

# Sydnee App Sydnee API

Programmatic access to Sydnee accounts, users, requests, and task templates. The API exposes 11 endpoints secured with bearer authentication.

## For AI agents

Programmatically create an account, list accounts. Covers 11 operations with bearer authentication.

## Scope

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

## Capabilities

- Create an Account
- List Accounts
- Get Account
- Delete Account
- Add User to Account
- Remove User from Account

## Use cases

### Productivity Operations

Use the Sydnee API to perform productivity operations programmatically. The API provides 11 endpoints covering core functionality including create an account, list accounts, get account.

Example prompt: Call POST /accounts to create an account

### Automated Accounts Management

Automate accounts operations by combining multiple Sydnee API endpoints. Agents can list accounts and then get account in a single workflow.

Example prompt: Call GET /accounts to list accounts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sydnee 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 'create an account', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/accounts` | Create an Account |
| GET | `/accounts` | List Accounts |
| GET | `/accounts/{accountId}` | Get Account |
| DELETE | `/accounts/{accountId}` | Delete Account |
| POST | `/accounts/{accountId}/users` | Add User to Account |
| GET | `/accounts/{accountId}/users` | List Account Users |
| DELETE | `/accounts/{accountId}/user/{userId}` | Remove User from Account |
| POST | `/accounts/{accountId}/task-templates/{taskTemplateId}` | Assign Task Template to Account |

## Key resources

- **Accounts** — Account management
- **Users** — User management within accounts
- **Task Templates** — Task template operations
- **Requests** — Request management using templates

## 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:** 73 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 72 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/sydnee.app/sydnee/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 Sydnee API by hand means learning its bearer token scheme, pointing at the public-api.sydnee.app host, and writing the request and error handling for its account and user operations yourself. Through Jentic you install once, import Sydnee from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Sydnee puts the account id in the URL path (`/accounts/{accountId}`), so a rule can pin your agent to one account: it can read that account and manage its users and nothing else. You choose the operations it may call, so destructive ones like deleting an account or removing a user are not included unless you add them.
- **Credential handling:** Your Sydnee bearer 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 'create an account' or 'add a user to an account', and Jentic returns the matching Sydnee 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 Sydnee API use?

The Sydnee 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 create an account with the Sydnee API?

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

### What are the rate limits for the Sydnee 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 create an account through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an account'. Jentic returns the matching Sydnee API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Sydnee API have?

The Sydnee API exposes 11 endpoints covering accounts, users, task templates operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sydnee operations and credentials the agent may use. Since Sydnee carries the account id in the URL path (`/accounts/{accountId}`), you can pin the agent to a single account so it only reads that account and manages its users. You also choose the exact operations it may call, so destructive ones like DELETE `/accounts/{accountId}` or removing a user stay off unless you explicitly grant them.