Use the Marketplace to bring another service into a Darwinium journey: verify a bot challenge during login, assess an identity at registration, enrich an address at checkout, or send a selected event to a downstream system. You can combine these results with Darwinium's device, behavior and journey signals in the same decision.
A package installs editable files into your Workflows workspace. Most integrations contain reusable snippets: templates for an API call, HTML injection or complete journey step. You import the template, add it to the relevant interaction and supply its settings. Your reviewed configuration then follows the normal build and deployment process.
Start with the interaction you want to protect
For a website, start with your CDN integration. It lets Darwinium observe and act at the edge across the site's touchpoints. Use the Journey Recorder to map registration, login, checkout and other interactions, then add integrations where their information or action is useful.
For example, a registration journey can map an email and IP address, call an identity service, and use the returned intelligence alongside browser signals. A later step can create a case only when your decision requires review. Each service has a deliberate place in the flow; you do not need to call every provider on every request.
Choose an integration
| Your objective | Guide | What the package contributes |
|---|---|---|
| Check a bot challenge | Cloudflare Turnstile | Server-side token verification and response mappings |
| Add a challenge and verify its token | Google reCAPTCHA v2 | Separate widget, browser code and verification templates |
| Assess an identity or transaction | Ekata | Account opening and transaction risk lookups |
| Assess an email address | AtData | Email verification and intelligence lookups |
| Enrich an identity with network and device insights | Deduce | An Insights request and mapped trust, information and risk signals |
| Locate a supplied address | Google Geocoding | Address-to-coordinate lookup |
| Create a review task | Jira | An editable issue-creation request |
| Notify a customer | Twilio | An SMS request and its immediate result |
| Adapt another API service | RapidAPI examples | BIN, email and geocoding request patterns |
Provider subscriptions and credentials are supplied through your own provider accounts. The individual guides identify the supported API operation, required inputs and any changes needed to the installed template.
Add collection, messaging or detection
| Your objective | Guide |
|---|---|
| Collect browser and behavioral data | Browser profiling packages |
| Show a contextual warning or acknowledgement | Dynamic Messaging |
| Generate an initial detection model | Detection model templates |
| Extend an AssemblyScript model | AssemblyScript model helpers |
From installation to a working journey
- Install and attach the integration. Choose the step where its inputs are available.
- Connect credentials on the deployment target when the service requires authentication.
- Follow the integration's guide to map inputs, configure the request and inspect its outputs.
- Connect those outputs to a decision, or condition a downstream action on an existing decision.
- Deploy to a test target and exercise the real interaction. Confirm the event shows both the provider result and the intended Darwinium behavior.
To connect an internal API or reuse your own configuration, continue with Making your own integrations. Snippet references and arguments explains the template format and its different scopes.