How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Skyvia Public API

REST management API for the Skyvia platform. Programmatically read and control account users and invitations, workspaces and workspace membership, on-premise agents, data-source connections, data integration packages and their executions and schedules, automations and their execution history, cloud backups and snapshots, and Skyvia Connect endpoints and their request logs. Authenticated with a scoped Skyvia API token passed in the Authorization header; tokens carry per-resource read/execute/modify scopes and cannot be issued for longer than one year.

This API exposes 6 operations across 4 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.skyvia.com.

6 operations 4 paths 9 schemas 2 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.skyvia.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Skyvia Public API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Access_Token). By default, every request must be authenticated.

  • Access_Token — Authorization header with the Skyvia access token.

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 2 DELETE, 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Account 6

Account-level user and invitation management for the Skyvia account.

GET
/v1/account/users
Get account users
3 params → 200
DELETE
/v1/account/users
body → 200
GET
/v1/account/invitations
Get account invitations
2 params → 200
POST
/v1/account/invitations
body → 200
POST
/v1/account/invitations/{invitationId}/resend
1 param → 200
DELETE
/v1/account/invitations/{invitationId}
1 param → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are AccountInvitedUserDto (7 properties), AccountUserDto (5 properties), InviteUserRequestDto (3 properties), AccountWorkspaceUserDto (3 properties). Each schema is shown below with its type and property counts.

AccountUserDtoHasMorePagingDto
object
2 properties
InvitedUserStatusDto
object
3 properties
AccountWorkspaceUserDto
object
3 properties
InviteUserRequestDto
object
3 properties 2 required
AccountInvitedUserDto
object
7 properties
AccountInvitedUserDtoHasMorePagingDto
object
2 properties
RemoveAccountUserRequestDto
object
1 property
InviteToWorkspaceDto
object
2 properties 2 required
AccountUserDto
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

skyvia-account-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Skyvia Public API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.