Aduana Digital de Defensa Argentina
Create ADDA access
← ADDA Manual

sdk/1.1.0 · updated Jul 9, 2026

Integrations and SDK

First paths for connecting sensors, receiving signals, and consuming the ADDA assessment.

The integrations manual shows how to connect sensors, trust queries, evidence, and reputation modules using a shared reference.

A good integration does not end when the endpoint responds. It also requires validating format, governance, traceability, and how the new source affects tasks, incidents, automations, and the living manual.

Use this guide to turn a technical connection into a real operational capability within ADDA.

Checklist

  • • Register the sensor or domain before enabling production ingestion.
  • • Test the trust assessment and evidence recording with controlled cases.
  • • Document common integration errors.

Quickstart

  1. 1. Register the source or domain to integrate first.
  2. 2. Test a minimal end-to-end flow before considering the integration ready.
  3. 3. If the integration leaves a recurring question, turn it into a manual candidate.

Operational flow

Connect

Register the sensor, source, or module that will push signals.

Define the integration's technical and operational identity.

Validate

Check that events, scores, or evidence use a format that is useful to ADDA.

Verify that the assessment actually enters the correct flow.

Productize

Link the integration to docs, the manual, tasks, or automations when applicable.

Avoid integrations isolated from the rest of the product.

flowchart LR
  S1["Connect"]
  S2["Validate"]
  S3["Productize"]
  S1 --> S2
  S2 --> S3

Validators and checks

They run a contextual reading for this surface and return suggested steps with an operational focus.

Validate the integration path

Summarizes articles and next steps for technical and operational onboarding.

Examples

Minimum event for ingestion

{
  "type": "sensor.alert",
  "source": "adda-agent-demo",
  "severity": "yellow",
  "summary": "Se detecta actividad anómala en endpoint observado."
}

Links and references

APIs

  • /api/adda/v1/sensors
  • /api/adda/v1/sensors/register
  • /api/adda/v1/events/ingest

Docs and supporting routes

  • docs/ADDA_API.md
  • docs/ADDA_MANUAL.md

Common issues

  • • Connecting a source without operational validation usually creates more noise than coverage.
  • • Failing to document common errors makes the team repeat diagnoses.

Suggested actions

  • • Productize the integration with quickstarts, examples, and visible routes.
  • • Promote any recurring onboarding gap to a manual candidate.

Useful reason codes

Score dictionary

severity

Institutional priority of the signal on the ADDA scale.

action

Next operational step recommended by the engine.

reasonCodes

Explainable reasons that justify the assessment.

Protocol notes

  • • A ready integration enters operational flows, not only the API.

Article history

Jul 9, 2026

Expanded the article with an integration quickstart and ingestion example.