canonical: https://jentic.com/apis/spiky.ai/spiky

# Spiky API V2

Spiky API V2 provides programmatic access to Spiky's meeting analysis platform. How to use: 1. Open a Spiky account 2. Get authentication tokens 3. Send POST `/platform/meeting-reports` for fetching upload URLs. The integration name must be given "MANUALTIMELINE" for manual timeline upload flow. 4. Upload timeline file to S3 via given signed URL (if manual timeline flow is selected) 5. Upload a vide. The API exposes 6 endpoints secured with bearer authentication.

## For AI agents

Programmatically get an authorization token, refresh an authorization token. Covers 6 operations with bearer authentication.

## Scope

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

## Capabilities

- Get an authorization token
- Refresh an authorization token
- Create a new analysis
- List analyses
- Monitor Spiky API V2 operational status and events

## Use cases

### Productivity Operations

Use the Spiky API V2 to perform productivity operations programmatically. The API provides 6 endpoints covering core functionality including get an authorization token, refresh an authorization token, create a new analysis.

Example prompt: Call POST `/public/token` to get an authorization token

### Automated authorization Management

Automate authorization operations by combining multiple Spiky API V2 endpoints. Agents can refresh an authorization token and then create a new analysis in a single workflow.

Example prompt: Call POST `/public/token/refresh` to refresh an authorization token, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Spiky API V2 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 'get an authorization token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/public/token` | Get an authorization token |
| POST | `/public/token/refresh` | Refresh an authorization token |
| POST | `/platform/meeting-reports` | Create a new analysis |
| GET | `/platform/meeting-reports` | List analyses |
| GET | `/platform/meeting-reports/{analysisId}` | Get an analysis by ID |
| GET | `/platform/ml-data/{analysisId}` | Get ML data for an analysis |

## Key resources

- **authorization** — Authorization operations
- **meeting-reports** — Meeting Report Endpoints
- **ml-data** — Machine learning model outputs

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/spiky.ai/spiky/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 Spiky API V2 by hand means implementing its bearer auth, calling its `/public/token` and refresh endpoints to keep a live token, and pointing every request at the apiv2.spiky.ai host yourself. Through Jentic you install once, import Spiky API V2 from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Spiky puts the analysis id in the URL path (`/platform/meeting-reports/{analysisId}`), so a rule can pin your agent to one meeting report and its ml-data. You choose the operations it may call, so creating new meeting reports is not included unless you add it.
- **Credential handling:** Your Spiky 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 'list meeting reports' or 'get analysis data for a meeting', and Jentic returns the matching Spiky API V2 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 Spiky API V2 use?

The Spiky API V2 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 get an authorization token with the Spiky API V2?

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

### What are the rate limits for the Spiky API V2?

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 get an authorization token through Jentic?

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

### How many endpoints does the Spiky API V2 have?

The Spiky API V2 exposes 6 endpoints covering authorization, meeting-reports, ml-data operations.

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

Yes. Jentic One runs self-hosted, so your own rules decide which Spiky operations and credentials your agent may use. Because Spiky puts the analysis id in the URL path (`/platform/meeting-reports/{analysisId}`), you can pin the agent to a single meeting report and its ml-data instead of the whole account. You also choose the exact operations it may call, so read-only access to List analyses and Get an analysis stays separate from Create a new analysis, which is excluded unless you grant it.