The interface is yours.
Web, native app, internal portal or conversational channel. Organize the experience in your frontend and expose through your backend only what that journey needs.
CATALISA / DEVELOPERSYour code.
Your code.
More possibilities.
From a single API call to an entire product. Connect capabilities to what you've already built — or use this foundation to start something new.
// what makes your product uniqueyour.product()A representation of composition, not SDK syntax.
interfacedomainexperience
catalisaconnect()
01 identity
02 decision
03 payments
04 documents
05 ai
06 events
START IN YOUR CONTEXTThe best integration
The best integration
fits into your system.
You choose the boundary. A building block to handle one responsibility, a composition to support a journey, or the platform as the foundation for a new product.
ADOPTION PATTERN / 01
Your next product. Your experience.
Build the interface and rules that set your business apart. Compose identity, decisioning, documents and communication behind it. The first scope can be an entire journey or just a single operation.
- You keep
- Interface, domain and product strategy
- You connect
- Selected capabilities and integrations
Example: a credit proposal originates in your interface, goes through the published policy and moves on to formalization. You define the experience, the domain data and the approval points.
Illustrative reference architecture. The scope depends on each capability's contract.HTTP. JSON. YOUR STACK.Less guesswork.
Less guesswork.
More contract.
Consume the API with the tools your team already uses. Each capability has its own operations, inputs, permissions, and limits.
Integration examples based on the documentation. Configure credentials and resources in your environment before running. This page does not send requests.
POST
/decision-engine/api/v1/decisions/{decisionId}/execute# Configure a URL e o token do seu ambiente.
# Substitua {decisionId}, quando aplicável.
curl --fail-with-body --request POST \
"$CATALISA_BASE_URL/decision-engine/api/v1/decisions/{decisionId}/execute" \
--header "Authorization: Bearer $CATALISA_TOKEN" \
--header "Content-Type: application/json" \
--data '{
"input": {
"age": 25
}
}'Sample input for an age decision. Requires an ACTIVE decision and a published version; the input fields belong to your DMN table.
Full contract and prerequisites ↗FLEXIBILITY WITH CLEAR BOUNDARIESPluggable where it matters.
Pluggable where it matters.
Your product in control.
The provider may change.
Blocks with drivers decouple the operation from the vendor. In AI Engine, provider selection is configurable; in Payments and BaaS, check the supported adapters and operations before integrating.
Explore providers ↗The scope can grow.
Start with the decision. Add documents when it makes sense. Connect communication later. Validate each block's dependencies and evolve in stages your team can operate.
ARCHITECTURE RECIPESWhat you want
What you want
get off the ground?
Composition ideas to get past the blank page. The flows below are integration proposals, not ready-made packages.
Credit inside your product
Your screen receives the application. Your backend prepares the data, calls the decision and forwards it for formalization when the policy allows.
Keep limits, approval authority and exceptions explicit.Banking with its own identity
An account experience with your own design and navigation. Compose the app's front door with the financial operations offered by the enabled providers.
Define who records each operation and how to reconcile the result.AI in the customer service you already have
Your CRM receives the message. A call classifies the intent; the application uses that result to suggest a queue or a next action, with review in the cases defined by the business.
Separate suggestion from execution and keep the authorized context.A new feature in your app
Add a simulation or a verification step without redesigning the entire navigation. Your BFF translates the API response into the mobile experience.
Assess privacy, permissions and the stage of each block.FROM THE FIRST REQUEST TO OPERATIONSCode integrates.
Code integrates.
The contract holds it up.
EVENT DELIVERY / CONCEPTUAL VIEWThe event has
The event has
a way back.
- 01An action happensin the source block
- 02A subscription selects eventsin the Webhooks Engine
- 03Your endpoint receivesvalidates the signature and processes with idempotency
- 04Delivery leaves a historyreview attempts and investigate failures
Credentials with intent
Use IAM and the authentication mechanism appropriate to the contract. API Keys lets you scope access by route and manage rotation and revocation. Service credentials stay on the backend.
Reference ↗Organization context
Resolve the organization from the authorized identity. The application must preserve this boundary when calling the blocks and when persisting its own data.
Reference ↗Versions that explain decisions
In the Decision Engine, policies are versioned and every execution leaves a record. Plan regression cases before publishing a new policy.
Reference ↗Failures planned for in the design
Define timeouts, error handling and a recovery strategy. For events, validate the signature and avoid repeating business effects when a delivery is resent.
Reference ↗YOUR FIRST SCOPEChoose a responsibility.
Choose a responsibility.
Build from it.
01
Find the piece
Choose the domain and check the capability's stage.
02
Read the contract
Validate authentication, dependencies, inputs, and responses.
03
Integrate a journey
Test the happy path, the failures and the effects on your system.
Production, Beta and Alpha indicate different stages. Availability, dependencies and scope should be confirmed in each block's documentation.