Connect your services to Darwinium, submit events, maintain feedback, and make event data available to your analytics tools.
Choose the direction of integration
| Your task | Where the request goes | Guide |
|---|---|---|
| Submit an interaction for Darwinium assessment | Your backend → Darwinium | Event API |
| Enrich an event or trigger a downstream action | A Darwinium journey → another service | Darwinium Marketplace |
| Supply confirmed outcomes or later information | Your service → Darwinium | Label API and Update API |
| Analyze event data outside the portal | Darwinium data → your analytics destination | Data exports |
For supported CDN traffic, begin with CDN / edge integration. A direct Event API call is useful when your backend submits the interaction or needs to contribute origin-only context.
Make your first API request
- Set up Certificates & API access. The guide covers creating a certificate signing request, obtaining a signed certificate, and assigning access to the required nodes and services.
- Create and deploy the API step that will process your request, then read the Event API for the request and response format.
- Adapt an example from API examples: cURL, Postman & languages.
- Use Investigations to review the resulting event.
Choose the API for your task
- Submit an event for assessment: Event API.
- Update an existing event: Update API.
- Manage labels and feedback: Label API and Labels & feedback.
- Deploy an API endpoint in your infrastructure: API Outpost.
Connect other systems
Use Data exports to choose an S3, Databricks, Snowflake, or notebook workflow. Use Account takeover protection to integrate Darwinium risk assessment with your customer identity provider and apply risk-based authentication. To configure employee access to the Darwinium portal, see Portal single sign-on.
Looking for a field definition? Open the Attribute Reference. If you are choosing an integration method, review the recommended CDN / edge route in Install & collect.
Observe MCP and JSON-RPC endpoints
Use Monitor MCP and JSON-RPC traffic to protect your application's HTTP endpoint through the CDN, distinguish individual tool calls and map their arguments and results. This is separate from submitting an Event API request to Darwinium, and from using the Portal MCP assistant.