Custom Integrations

Connect any API to empower your AI agent with real-time data and actions

Custom integrations let you connect Cevro to any system with an API. Your back-office, CRM, internal tools, payment processors, third-party services—if it has an API, your AI agent can use it.

Why Custom Integrations?

You’re not limited by what Cevro supports out of the box. Custom integrations give your AI agent the ability to:

• Fetch data from any system — player info, transaction history, account status, inventory, anything
• Take actions — issue bonuses, update records, trigger workflows, send notifications
• Make decisions using real-time information from your actual systems

This is how your AI agent goes from “I can look that up for you” to actually doing the work. The same capabilities your human agents have, now available to your AI.

Overview

Navigate to Settings → Integrations to view your integrations. Custom integrations appear in their own section.

If you don’t see custom integrations, reach out to your CSM to enable this feature.

Each custom integration is a container for operations—individual API endpoints the AI can invoke. For example, a “Back-Office API” integration might contain:

• Player Info
• Player Balances
• Active Bonuses
• Deposits
• Withdrawals

Getting Started

Creating an Integration

1. Click Add Custom Integration
2. Enter a name and optional description
3. Add operations (see below)

Configuring Operations

Each operation represents a single API endpoint. Click an operation to configure it through these tabs:

Create Tab

Setting	Description
Display Label	Human-readable name (e.g., “Player Deposits”)
Name	Auto-generated identifier from the label
Data Type	READ for fetching data, WRITE for actions that modify data
Available From	Where this operation can be used: AIP (AI Procedures), Rule Trigger (automation rules)

Integrate Tab

Setting	Description
Endpoint	The API URL—supports dynamic values like {{workspace.boApiUrl}}/v1/player
HTTP Method	GET, POST, PUT, PATCH, or DELETE
Parameters	Request parameters (see Parameters below)
AI Instructions	Describe what this operation does—helps the AI know when and how to use it
Headers	Optional custom HTTP headers

Authenticate Tab

Setting	Description
IP Allowlist	Cevro’s outbound IPs—add these to your API’s firewall if needed
Requires Authentication	When enabled, players must be authenticated before this operation runs

Preview Tab

Test your operation:

1. Choose Run API to test against your real API, or Manual JSON to paste a sample response
2. Fill in test values for dynamic parameters
3. Click Run Test
4. Review the response

Run API mode calls your production API. Be careful with operations that modify data.

Code Transformation Tab

Transform API responses before they reach the AI:

• RAW mode passes the response through unchanged (recommended for most cases)
• CODE mode lets you write JavaScript to transform the response

Save Tab

Review and save your configuration.

Parameters

Parameters define what data gets sent with each API request.

Internal Parameters

Values the system provides automatically. Set a value using:

• Fixed values (e.g., 50 for a limit)
• Dynamic values (e.g., {{contact.email}}, {{brand.slug}}, {{workspace.boApiUrl}})

See Dynamic Values for the full reference of available tags.

External Parameters

Values the AI determines at runtime based on the conversation. Leave the value empty and write a clear description so the AI knows what to ask the player or infer from context.

Example: A “transaction lookup” operation might have an external transaction_id parameter with description: “The transaction ID the player wants to inquire about.”

Field Catalog

The field catalog defines what data from API responses is available to the AI.

Auto-Discovery

After running a test in the Preview tab:

1. Click Auto-Discover
2. Cevro analyzes the response and creates fields with AI-generated labels and descriptions
3. Review and customize as needed

Fields are also discovered at runtime—when an operation returns new fields, they’re automatically cataloged.

Customizing Fields

For each field, you can:

• Edit the label (display name)
• Edit the description (helps the AI understand the field)
• Hide fields that shouldn’t surface to the AI

Workspace-Level Settings

Some settings are configured at the workspace level:

Setting	Description
Back-Office API URL	Base URL available as {{workspace.boApiUrl}}
Authentication	How API requests are authenticated (bearer token, API key, etc.)
Player Authentication	How players verify their identity

Reach out to your CSM if you need these adjusted.

Troubleshooting

Fields not appearing in AIP builder

• Enable Available From: AIP on the Create tab
• Check the field isn’t hidden in the catalog
• Run Auto-Discover after testing

Test returns unexpected results

• Check the Endpoint URL (no missing slashes)
• Verify parameter names match your API exactly (camelCase vs snake_case)
• Review the full response in Preview

Building Your API

If you’re building a custom API for Cevro to consume, see Connect Your Back-Office for endpoint patterns, authentication flows, and best practices.

Related Documentation

• Dynamic Values — Reference for interpolation tags
• Connect Your Back-Office — API specification for custom integrations
• Player Authentication — How players verify their identity