Do I need a separate product for integrations?

No. Use /api/v1 with a scoped key. See /docs/api and the REST API feature page.

What is a realistic first integration?

Closed-won deals → billing invoice, with payment status synced back to the deal record.

Can sync be read-only?

Yes. Issue a profile with view-only access and poll records into your warehouse or BI stack.

Connect billing, ERP, or custom apps with bidirectional sync

Any external system can stay aligned with OSTRATA—issue a scoped API key and let jobs push closes outbound while webhooks PATCH records when status changes elsewhere.

2-way

Sync pattern

Push closes, pull payment status

API

No UI required

Jobs call /api/v1 with scoped keys

ERP

Example flow

NetSuite invoice ↔ deal record

CRM meets your stack

Bidirectional sync with billing, ERP, or custom apps.

Spreadsheets and one-way Zapier flows break when finance and sales each own part of the truth. Bidirectional sync keeps deal stage, invoice ID, and payment status consistent without manual reconciliation.

Example: when a deal closes in OSTRATA, your middleware creates a NetSuite invoice. When NetSuite marks it paid, a webhook updates the deal record via PATCH /api/v1. Stripe, a warehouse, or internal ETL follow the same pattern.

Two-way truth
Outbound events and inbound updates on the same records.
Scoped keys
Integration runs as a permission profile—not root access.
Your schema
Custom fields for ERP IDs, payment flags, or sync timestamps.

Outbound

Outbound: CRM events drive your stack

React when pipeline reality changes in OSTRATA.

Poll deals on a schedule or trigger on stage = Closed Won
POST to billing, ERP, or fulfillment with mapped fields
Store external IDs back on the deal via API

Inbound

Inbound: external status updates CRM

Let payment, shipment, or provisioning webhooks write back.

PATCH deal or contact records when invoice pays
Update custom fields finance owns without Ops UI
Idempotent handlers—same webhook safe to retry

Scope

Governance that survives audits

Separate profiles for read-only analytics vs. write sync.

Dedicated key per integration with least privilege
Revoke without touching member logins
Field-level limits hide sensitive attributes from ETL

Questions

Short answers before you request access.

Do I need a separate product for integrations?: No. Use /api/v1 with a scoped key. See /docs/api and the REST API feature page.
What is a realistic first integration?: Closed-won deals → billing invoice, with payment status synced back to the deal record.
Can sync be read-only?: Yes. Issue a profile with view-only access and poll records into your warehouse or BI stack.