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

# Skyvia API

Skyvia is a cloud data integration, backup, and management platform. The Connect API (OData) exposes cloud and database data as REST endpoints. The Skyvia management API provides control over integrations, connections, and data pipelines. The API exposes 18 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a connection, list all connections. Covers 18 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create a connection
- List all connections
- Get a connection
- Update a connection
- Delete a connection
- Test a connection

## Use cases

### CRM Operations

Use the Skyvia API to perform crm operations programmatically. The API provides 18 endpoints covering core functionality including create a connection, list all connections, get a connection.

Example prompt: Call POST /connections to create a connection

### Automated Agents Management

Automate agents operations by combining multiple Skyvia API endpoints. Agents can list all connections and then get a connection in a single workflow.

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

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/connections` | Create a connection |
| GET | `/connections` | List all connections |
| GET | `/connections/{id}` | Get a connection |
| PUT | `/connections/{id}` | Update a connection |
| DELETE | `/connections/{id}` | Delete a connection |
| POST | `/connections/{id}/test` | Test a connection |
| GET | `/packages` | List integration packages |
| GET | `/packages/{id}` | Get a package |

## Key resources

- **Agents** — Operations related to Agents
- **Backups** — Operations related to Backups
- **Connect** — Operations related to Connect
- **Connections** — Operations related to Connections
- **Packages** — Operations related to Packages

## 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:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 66 / 100
- **View full report:** https://jentic.com/apis/skyvia.com/skyvia/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 Skyvia by hand means sending a bearer token in the Authorization header to app.skyvia.com/api and managing the connections and packages calls yourself. Through Jentic you install once, import Skyvia from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Skyvia puts the connection id in the URL path (`/connections/{id}` and `/connections/{id}/test`), so a rule can pin your agent to one connection. You choose the operations it may call, so destructive ones like connection deletion are not included unless you add them.
- **Credential handling:** Your Skyvia 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 my connections' or 'test a connection', and Jentic returns the matching Skyvia operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Skyvia API use?

The Skyvia API uses an API key passed 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 a connection with the Skyvia API?

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

### What are the rate limits for the Skyvia 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 a connection through Jentic?

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

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

The Skyvia API exposes 18 endpoints covering agents, backups, connect operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Skyvia operations and credentials the agent may use. Since Skyvia carries the connection id in the URL path, such as GET `/connections/{id}` and POST `/connections/{id}/test`, you can pin the agent to a single connection. You also pick which operations it may call, so a destructive one like DELETE `/connections/{id}` stays out of reach unless you add it.