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

# Scoro API

Scoro work management API. The API exposes 148 endpoints secured with apiKey authentication.

## For AI agents

Programmatically userauth modify, userauth delete. Covers 148 operations with apiKey authentication.

## Scope

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

## Capabilities

- userAuth modify
- companyAccount list
- contacts list
- Query and filter Scoro API records by parameters
- Monitor Scoro API operational status and events

## Use cases

### Developer Tools Operations

Use the Scoro API to perform developer tools operations programmatically. The API provides 148 endpoints covering core functionality including userauth modify, userauth delete, userauth versioncheck.

Example prompt: Call POST `/userAuth/modify` to userauth modify

### Automated Activities Management

Automate activities operations by combining multiple Scoro API endpoints. Agents can userauth delete and then userauth versioncheck in a single workflow.

Example prompt: Call POST `/userAuth/delete/{id}` to userauth delete, then verify the result

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/userAuth/modify` | userAuth modify |
| POST | `/userAuth/delete/{id}` | userAuth delete |
| POST | `/userAuth/versionCheck` | userAuth versionCheck |
| POST | `/userAuth/verify` | userAuth verify |
| POST | `/companyAccount/list` | companyAccount list |
| POST | `/contacts/list` | contacts list |
| POST | `/contacts/view/{id}` | contacts view |
| POST | `/contacts/modify/{id}` | contacts modify |

## Key resources

- **Activities** — Operations for activities
- **Addresses** — Operations for addresses
- **Bills** — Operations for bills
- **Bookings** — Operations for bookings
- **Calendar** — Operations for calendar

## 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:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 55 / 100
  - AI-Readiness & Agent Experience: 16 / 100
  - Agent Usability: 68 / 100
  - Security: 15 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/scoro.com/scoro/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 Scoro API by hand means passing your apiKey in the query string, resolving your per-company host at {company}.scoro.com, and building retries across its many list, view, and modify calls yourself. Through Jentic you install once, import Scoro from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Scoro puts the record id in the URL path (`/contacts/view/{id}` and `/contacts/modify/{id}`), so a rule can pin your agent to one contact: it can view or modify that record and nothing else. You choose the operations it may call, so destructive ones like contact deletion or userAuth deletion are not included unless you add them.
- **Credential handling:** Your Scoro API key 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 'list contacts' or 'view a contact by id', and Jentic returns the matching Scoro operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Scoro API use?

The Scoro API uses an API key passed in the `apiKey` query. 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 userauth modify with the Scoro API?

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

### What are the rate limits for the Scoro 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 userauth modify through Jentic?

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

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

The Scoro API exposes 148 endpoints covering activities, addresses, bills operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Scoro operations and credentials the agent may use. Since Scoro puts the record id in the URL path, such as `/contacts/view/{id}` and `/contacts/modify/{id}`, you can pin the agent to a single contact so it only views or modifies that record. You also choose the operations it may call, so destructive ones like contact deletion or userAuth deletion stay off the list unless you explicitly add them.