Skip to main content
The Plyne API is designed around the same jobs your team handles in the dashboard: find buyers showing intent, track accounts that matter, and pull the context needed for timely outreach. Setup stays in the dashboard. The API gives you a clean read layer for signal agents, qualified leads, monitored accounts, and account-level signal activity.

​
Sections

Signals

Intent Signals agents that continuously find buyers matching your ICP.

Monitor

Account monitoring for custom questions your team wants checked on a schedule.

Signal leads

Qualified leads with embedded company details and source context.

API Basics

Authentication, pagination, and shared filtering conventions.

​
Endpoint surface

​
Signals

MethodEndpointPurpose
POST/v1/signals/agentsList Intent Signals agents configured in the dashboard.
POST/v1/signals/leadsList leads surfaced by signal agents.

​
Monitor

MethodEndpointPurpose
POST/v1/monitor/accountsList target accounts being monitored.
POST/v1/monitor/resultsList account signals found while monitoring target accounts.

​
Later

MethodEndpointPurpose
GET/v1/signals/agents/{id}Read one signal agent.
GET/v1/monitor/accounts/{id}Read one monitored company.
GET/v1/monitor/results/{id}Read one monitoring result.
GET/v1/monitor/signalsList custom signal definitions used by Monitor.

​
Design constraints

  • No run-start endpoint for the basic API.
  • No create/update endpoints for signal setup in the first version.
  • Use filters on list endpoints instead of deep nested result endpoints.
  • Keep endpoint names aligned with dashboard terminology.