--- title: "APIs & integrations | Darwinium" slug: "apis-integrations" description: "Choose between calling Darwinium APIs, invoking downstream services from journeys, supplying feedback and exporting event data." updated: 2026-10-16T10:21:04Z published: 2026-10-16T10:21:04Z canonical: "docs.darwinium.com/apis-integrations" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.darwinium.com/llms.txt > Use this file to discover all available pages before exploring further. # APIs & integrations 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](/docs/event-api) | | Enrich an event or trigger a downstream action | A Darwinium journey → another service | [Darwinium Marketplace](/docs/darwinium-marketplace) | | Supply confirmed outcomes or later information | Your service → Darwinium | [Label API](/docs/label-api) and [Update API](/docs/update-api) | | Analyze event data outside the portal | Darwinium data → your analytics destination | [Data exports](/docs/exporting-to-analytics-platforms) | For supported CDN traffic, begin with [CDN / edge integration](/docs/cdn-deployment). 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 1. Set up [Certificates & API access](/docs/setting-up-certificates). The guide covers creating a certificate signing request, obtaining a signed certificate, and assigning access to the required nodes and services. 2. Create and deploy the API step that will process your request, then read the [Event API](/docs/event-api) for the request and response format. 3. Adapt an example from [API examples: cURL, Postman & languages](/docs/example-api-code). 4. Use [Investigations](/docs/investigations-overview) to review the resulting event. ## Choose the API for your task - **Submit an event for assessment:** [Event API](/docs/event-api). - **Update an existing event:** [Update API](/docs/update-api). - **Manage labels and feedback:** [Label API](/docs/label-api) and [Labels & feedback](/docs/labels). - **Deploy an API endpoint in your infrastructure:** [API Outpost](/docs/setting-up-api-outpost). ## Connect other systems Use [Data exports](/docs/exporting-to-analytics-platforms) to choose an S3, Databricks, Snowflake, or notebook workflow. Use [Account takeover protection](/docs/iam-integration) 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](/docs/establishing-sso). Looking for a field definition? Open the [Attribute Reference](/docs/attribute-reference). If you are choosing an integration method, review the recommended [CDN / edge route](/docs/cdn-deployment) in [Install & collect](/docs/installation). ## Observe MCP and JSON-RPC endpoints Use [Monitor MCP and JSON-RPC traffic](/docs/monitor-mcp-jsonrpc-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](/docs/mcp-overview).