Recipes
Recipes
This page is the public entry point for common Corebanq API recipes. Recipes describe end-to-end business tasks and point to API references without exposing customer-specific licensing or proprietary extensions.
Authentication First
Most recipes start with the same integration setup:
- Create application credentials.
- Request an access token.
- Send authenticated API requests with traceable request IDs.
- Handle standard error responses.
- Store audit-friendly references for reconciliation.
Common Recipe Pattern
Use the same structure for each recipe:
| Section | Purpose |
|---|---|
| Business goal | What the integration user wants to complete. |
| Actors | User, operator, or system roles involved. |
| Preconditions | Required account, customer, permission, and configuration state. |
| API sequence | Endpoint sequence and important state transitions. |
| Result | Expected records, events, and user-visible status. |
| Failure handling | Validation, retry, and support path. |
Recipe catalog
End-to-end integration flows with sequence diagrams.
Customer-specific recipes are published only inside the matching customer site.