Aduana Digital de Defensa Argentina
Create ADDA access
← ADDA Manual

api-shield/1.0.0 · updated Jul 9, 2026

API protection

How to operate rate limits, reputation, and integration routes without losing visibility.

API Shield protects integration routes, automations, and programmatic consumption with an assessment distinct from that of a human-operated form.

The priority is not only to block anomalous requests: it is also necessary to avoid breaking valid integrations, distinguish institutional traffic from scraping, and preserve Evidence when a limit affects a relevant service.

Cross-checking API Shield with Access, WAF, and Secrets helps address cases where the risk lies not in one request but in the credential, tunnel, or source posture.

Checklist

  • • Identify critical integration routes.
  • • Check whether the source uses known credentials, tunnels, or sessions.
  • • Support the decision with Evidence if it changes service continuity.

Quickstart

  1. 1. Start from the integration route, not only the isolated request.
  2. 2. Check whether the API is linked to Secrets, Access, or active credentials.
  3. 3. Use tasks when the adjustment requires coordination with another area.

Operational flow

Establish context

Read the route, source, and expected service continuity.

Avoid blind blocking on APIs with downstream dependencies.

Relate signals

Cross-check the signal with Secrets, Access, or keyring to determine whether trust changed.

Determine whether the problem is traffic, identity, or a credential.

Agree on a response

Create a task or incident when mitigation involves several teams.

Maintain governance over sensitive changes.

flowchart LR
  S1["Establish context"]
  S2["Relate signals"]
  S3["Agree on a response"]
  S1 --> S2
  S2 --> S3

Validators and checks

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

Validate API protection

Returns checks and articles for integrated or automated routes.

Examples

Payload for reviewing an exposed API

{
  "moduleKey": "api-shield",
  "query": "token reuse scraping",
  "domain": "api.capacero.ar"
}

Links and references

APIs

  • /api/adda/v1/shields/events
  • /api/adda/v1/secrets/status
  • /api/adda/v1/access/status

Docs and supporting routes

  • docs/ADDA_API.md
  • docs/ADDA_WAF.md

Common issues

  • • Treating programmatic traffic as human browsing disrupts the response.
  • • Adjusting the defense without reviewing Secrets or Access can leave the cause of the risk active.

Suggested actions

  • • Always cross-check the signal against related credentials, sessions, or tunnels.
  • • If an API supports critical processes, prioritize limiting and traceability before abrupt blocking.

Useful reason codes

Score dictionary

wafRiskScore

Risk detected on the observed route or form.

decision

Decided action: allow, verify, limit, or block.

matchedRules

Rules that explain why protection was activated.

Protocol notes

  • • Service continuity matters as much as containing abuse.

Article history

Jul 9, 2026

Added an API Shield article focused on continuity, credentials, and coordination.