Welcome to the Pipeium API documentation
The Pipeium API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
All API requests should be made to:
The Pipeium API uses API keys to authenticate requests. You can view and manage your API keys in the Pipeium Dashboard.
All API requests must include your API key in the Authorization header:
The API has rate limits based on your plan:
Rate limit headers are included in all API responses:
X-RateLimit-Limit
: Total requests allowed per hourX-RateLimit-Remaining
: Remaining requests for the current hourX-RateLimit-Reset
: Time when the rate limit will reset (Unix timestamp)The Pipeium API uses conventional HTTP response codes to indicate the success or failure of an API request:
2xx
: Success4xx
: Client errors5xx
: Server errorsCommon error codes:
400
: Bad Request - Invalid request body or parameters401
: Unauthorized - No valid API key provided403
: Forbidden - API key doesn’t have permission404
: Not Found - Resource doesn’t exist429
: Too Many Requests - Rate limit exceeded500
: Internal Server Error - Something went wrong on our endError response format:
Pipeium can send webhook notifications when certain events occur. Configure webhooks in the dashboard or when creating resources that support notifications.
Webhook requests will include:
X-Pipeium-Signature
: HMAC SHA-256 signature of the payloadX-Pipeium-Event
: Type of event (e.g., enrichment.completed
, signal.triggered
)Lists API
Enrichment API
Signals API
Settings API
Need help? Contact us: