Skip to main content
Prophic integrations let you start Quick Quotes from outside the web app, then either wait for webhook notifications or poll for status. The same AI pipeline runs behind the scenes, so the proposal you get back is identical to a UI-generated one. Use this when you want to:
  • Kick off a Quick Quote from your CRM the moment an RFP lands.
  • Feed briefs from a customer portal or intake form into Prophic automatically.
  • Trigger downstream automation (Slack alerts, Notion entries, deal-stage updates) when a proposal is ready.

​
How it fits together

API Keys

Create a key from Account, then call the integrations API with X-API-Key.

Webhooks

Get notified when pipeline steps finish, without polling.

API Reference

Full contracts for the partner integrations and webhook config APIs.

Quick Quotes

Learn the product flow that runs behind every headless quote.
Headless Quote. A Quick Quote started with an API key instead of the web app. It runs the same pipeline; only the source field is stored as api_key so webhooks can tell partner traffic apart from UI activity.

​
Typical flow

1

Create an API key

Open Account → API Keys, name the key (for example Salesforce production), set an expiry, and copy the pk_... value once. Store it in your secret manager.
2

Start a Quick Quote

POST /v1/integrations/quotations with requirementsText and/or up to five files. You get back a 202 and a quotation_id immediately.
3

Wait for webhooks or poll status

Subscribe to events like quotation.proposal.completed or call GET /v1/integrations/quotations/:id and /pipeline on an interval.
4

Fetch the proposal

When the proposal is ready, call GET /v1/integrations/quotations/:id/proposal, then GET /v1/integrations/proposals/:id/document-url for a short-lived download URL.

​
What you need

  • An organization in Prophic.
  • Permission to create your own API keys. Every org member has this by default.
  • Manage integrations (manage_integrations) if you will configure webhooks or manage other people’s keys. Org admins have it by default.
  • An HTTPS URL that can receive POST requests, if you plan to use webhooks.

​
Design principles

  • Async by default. The integrations path never blocks; every start returns 202 and you receive results via webhooks or polling.
  • Lean webhook payloads. Bodies carry IDs and status only, never the full proposal. Fetch the details through the API after a notification.
  • Scoped by key. Every request is scoped to the organization the key belongs to. Client-supplied organization IDs are ignored.

​
Next steps

Create your first API key

Set up authentication for a headless integration.

Configure webhooks

Receive pipeline notifications and verify signatures.