Connect API keys and webhooks
Create psv_ API keys on Pro+, register HTTPS webhooks on Business+, verify HMAC signatures and run a test delivery.
Automation starts in Settings after your plan unlocks the feature. API access is Pro and above. Outbound webhooks are Business and Enterprise.
API keys
Owners create keys under Settings → API keys. Copy the psv_ secret once - Prosvera stores only a hash. Send it as X-Api-Key or Authorization: Bearer. Include X-Organization-Id when using a user JWT across multiple workspaces; keys are already org-bound.
- Base path: https://platform.prosvera.space/api
- Common calls: discovery jobs, leads, campaigns, messages
- Keys consume API_REQUEST usage on your plan
Webhooks
Register an HTTPS URL, keep the generated secret, and subscribe to the events you need: discovery.completed, lead.created, campaign.started, email.sent. Use the Test action to receive webhook.test.
Every delivery includes X-Prosvera-Signature: sha256=<hmac> over the raw body and User-Agent: Prosvera-Webhooks/1.0. Verify the signature with a constant-time compare before you trust the JSON. Full detail is on the API page.
Safety
Never commit keys or webhook secrets. Rotate on suspicion. Do not use automation to bypass human approval or suppressions - those controls exist for legal and brand reasons.
Tell Prosvera who you want to sell to.