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

Screenpipe Cloud Sync API

Sync data across devices via cloud

Screenpipe Cloud Sync API is one of 18 APIs that Screenpipe publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cloud Sync. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 7 operations across 7 paths, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against the base URL http://localhost:3030.

7 operations 7 paths 6 schemas 1 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
http://localhost:3030
Resource Areas
1

Paths & Operations 7

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

Cloud Sync 7

Sync data across devices via cloud

POST
/sync/init
Initialize cloud sync
sync_api_sync_init body → 200
GET
/sync/status
Get sync status
sync_api_sync_status → 200
POST
/sync/trigger
Trigger sync
sync_api_sync_trigger → 200
POST
/sync/lock
Lock sync
sync_api_sync_lock → 200
POST
/sync/download
Download synced data
sync_api_sync_download body → 200
POST
/sync/pipes/push
Push pipe configs to cloud
sync_api_sync_pipes_push → 200
POST
/sync/pipes/pull
Pull pipe configs from cloud
sync_api_sync_pipes_pull → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are SyncStatusResponse (6 properties), SyncInitRequest (4 properties), PipeSyncResponse (3 properties), SyncInitResponse (3 properties). Each schema is shown below with its type and property counts.

SyncDownloadRequest
object
Request to download data from other devices.
1 property 1 required
SyncDownloadResponse
object
Response from download operation.
3 properties 3 required
SyncInitResponse
object
Response from sync initialization.
3 properties 3 required
SyncStatusResponse
object
Response for sync status.
6 properties 6 required
SyncInitRequest
object
Request to initialize sync at runtime.
4 properties 4 required
PipeSyncResponse
object
Response from pipe sync operations.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

screenpipe-cloud-sync-api-openapi.yml Raw ↑

Other APIs Screenpipe publishes across the network.

Screenpipe Activity API
Screenpipe Audio API
Screenpipe Cloud Archive API
Screenpipe Data Management API
Screenpipe Data Retention API
Screenpipe Database API
Screenpipe Elements API
Screenpipe Experimental API
Screenpipe Frames API
Screenpipe Meetings API
Screenpipe Memories API
Screenpipe Search API
Where this information came from

This is an independent, third-party profile of Screenpipe Cloud Sync 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.