localhost:3030; for CLI commands see the guides.
Screenpipe serves a REST API on localhost:3030. Use this to integrate with any tool or build custom automations.
For copy-paste workflows, start with API recipes. For the full interactive API reference with request/response schemas, see the API reference tab.
Endpoints
Search & content
Frames & elements
Meetings & speakers
Memories
Devices & health
Tags
Retention & deletion
Search example
Search parameters
Related context
Passinclude_related=true alongside a tags filter to get the tags that
co-occur with the ones you asked for — the people, projects, and workflows that
show up in the same frames, calls, and memories — in a single call instead of
several follow-up queries:
person: → people,
project: → projects); values are ordered most-frequent first. Omit
tags and the block is skipped.
Content type guide
Start with
content_type=all. Add app_name, window_name, or time filters only after you confirm broad search returns data.
Common API mistakes
Debugging
Enable verbose logging
To troubleshoot issues, enable debug logging by setting theSCREENPIPE_LOG environment variable before starting Screenpipe:
macOS/Linux:
debug— detailed diagnostic informationinfo— general informational messages (default)warn— warnings only (less verbose)