One credential per integration
A token per connected system, with minimum scope. Revoking one never takes the others down.
Integration · Technical
REST API and webhooks.
Every brisk4 integration rests on these two mechanisms. The platform consumes APIs from your systems and also exposes its own API, so your team can build what it needs without waiting on a vendor roadmap.
Capabilities
What the API allows.
| Resource | Direction | Typical use |
|---|---|---|
| Send message | Your system → brisk4 | Fire a notification over official WhatsApp from an event in your backend. |
| Contacts | Bidirectional | Create, read and update contacts and their custom fields. |
| Conversations and history | brisk4 → your system | Export transcript, channel, duration and owner into your data warehouse or BI. |
| Inbound message webhook | brisk4 → your system | React in real time to what the customer writes, for logic that runs on your side. |
| Status webhook | brisk4 → your system | Delivered, read or failed: track delivery for every message sent. |
Technical standards
What goes live first.
- REST with JSON and OAuth 2.0REST endpoints over HTTPS, JSON payloads and OAuth 2.0 or application token authentication, scoped per resource and revocable at any time.
- Signed webhooks with retriesEvery delivery is signed so your server can validate its origin. A failed receipt triggers retries with backoff, losing no events.
- Idempotency and paginationCalls accept an idempotency key so retries never duplicate an operation, and listings are cursor-paginated.
Best practices
Method and prerequisites.
Staging environment
Every integration is validated in a test environment before any production call.
Observability
Call, latency and error logs available for your team to monitor integration health.
- Protocol
- HTTPS with TLS
- Format
- JSON
- Authentication
- OAuth 2.0 or application token
- Events
- Signed webhooks with retries and backoff
- Limits
- Rate limit per credential, sized in the contract
- Documentation
- Technical reference delivered at the start of rollout
Frequently asked questions
brisk4 API: questions.
Does brisk4 have its own API?
It does. The platform exposes a REST API over HTTPS, with JSON payloads and OAuth 2.0 or application token authentication. It allows sending messages, managing contacts and exporting conversation history into your system.
How do the webhooks work?
brisk4 notifies your server when an event happens: message received, delivery status, contact change. Every delivery is signed so you can validate its origin, and failures trigger retries with backoff.
Can my team build integrations on their own?
Yes. The technical reference is delivered at the start of rollout, and the API is designed for direct use by your development team, with no dependency on our roadmap for each adjustment.
Is there a call limit?
There is a rate limit per credential, sized according to the contracted volume. Calls accept an idempotency key, so a retry never duplicates the operation.
Talk to people who know APIs.
In the free assessment your technical team talks directly to ours, with no sales intermediary translating requirements.