Developer Hub / API (A7)

documentação das apis autonomous documento de api — autonomous referência das apis da stack autonomous, com foco no que está exposto pelos serviços de backend da suíte o conteúdo aqui foi levantado diretamente do código fonte oficial dos serviços no repositório corporativo, sem invenção de rotas ou parâmetros produto autonomous — plataforma de observabilidade, gestão de ativos, resposta e correlação de eventos público alvo desenvolvedores e equipes de integração da central it e de parceiros técnicos autorizados versão da api v1 (rotas sob /api; módulo pipeline expõe /api/v1) versão do documento 1 0 data de emissão setembro/2026 classificação uso interno da central it e de integradores autorizados objetivo descrever as apis rest expostas pelos serviços de backend do produto autonomous, permitindo que times técnicos internos e integradores autorizados consumam essas rotas para automatizar operações de observabilidade, gestão de ativos, correlação de eventos, orquestração de coletores e execução da esteira de dados (pipeline) justificativa a stack autonomous é composta por múltiplos serviços independentes que precisam se integrar entre si e com ferramentas de terceiros publicar de forma organizada, em um único documento, o contrato real das rotas http de cada serviço — método, caminho, agrupamento por controlador — reduz retrabalho de integração, evita chamadas conflitantes e garante que qualquer novo desenvolvedor consiga localizar rapidamente a rota necessária escopo do produto 3 1 objetivo da integração as apis do autonomous têm como objetivo permitir que sistemas de operação, dashboards, agentes de endpoint, coletores de rede e ferramentas de orquestração consumam e alimentem dados de ativos lógicos, identidade de ativos e observações de agente (assets/cmdb) eventos de segurança, correlações, alertas e regras de ação (center) descoberta de rede e ativos ainda não catalogados (discovery) execução de jobs da esteira de dados enriquecimento, matching, risco, sincronização com ferramentas externas (pipeline) 3 2 url base e convenções gerais todas as rotas de cada serviço são publicadas sob o caminho /api do backend correspondente o prefixo do host varia conforme o ambiente e a topologia de rede em que o autonomous foi implantado, e é definido pela equipe de infraestrutura na configuração do serviço as requisições e respostas são em json (content type application/json) o backend do autonomous center é uma aplicação spring boot que, por padrão, escuta na porta 8080 do serviço 3 3 autenticação o backend do autonomous center suporta dois modos de autenticação, controlados pela propriedade app security enabled do serviço ambiente de desenvolvimento (app security enabled=false, padrão) todos os endpoints são liberados sem autenticação um aviso é registrado no log do serviço no boot este modo destina se apenas a ambientes locais e homologação ambiente de produção (app security enabled=true) autenticação por jwt (oidc), atuando como resource server oauth2 os tokens devem ser emitidos pelo idp configurado em spring security oauth2 resourceserver jwt issuer uri (tipicamente keycloak) endpoints públicos (sempre liberados, mesmo com segurança habilitada) get /actuator/health get /actuator/health/ get /actuator/prometheus get /actuator/info regras de autorização específicas quando app security enabled=true get /api/collectors/ /version e get /api/collectors/ /config exigem escopo scope collector (identidade máquina do agente coletor) rotas sob /api/admin/ exigem role config admin (realm access roles do keycloak) qualquer outra rota sob /api exige apenas token jwt válido (authenticated) cabeçalho de exemplo de requisição autenticada authorization bearer \<token jwt> content type application/json 3 4 api — autonomous center backend spring boot que centraliza correlação de eventos, gestão de regras, configuração de ambientes e integração com opensearch e demais serviços da stack é o serviço com maior superfície de api da suíte action rule — base /api/action rules método endpoint get /api/action rules get /api/action rules/active get /api/action rules/origins get /api/action rules/rule names get /api/action rules/ post /api/action rules put /api/action rules/ delete /api/action rules/ post /api/action rules/validate post /api/action rules/simulate get /api/action rules/ /runs get /api/action rules/runs/ post /api/action rules/runs/ /approve post /api/action rules/runs/ /reject admin maintenance — base /api/admin/maintenance método endpoint get /api/admin/maintenance/counts post /api/admin/maintenance/wipe get /api/admin/maintenance/wipe/ agent observation — base /api/db/agent observation método endpoint post /api/db/agent observation ai provider — base /api/ai providers método endpoint get /api/ai providers get /api/ai providers/types get /api/ai providers/ post /api/ai providers put /api/ai providers/ delete /api/ai providers/ post /api/ai providers/ /default post /api/ai providers/ /test alert rule — base /api/alerts método endpoint get /api/alerts/rules post /api/alerts/rules put /api/alerts/rules/ delete /api/alerts/rules/ get /api/alerts/active post /api/alerts/ /explain asset discovery collector — base /api/asset discovery collectors método endpoint get /api/asset discovery collectors get /api/asset discovery collectors/active get /api/asset discovery collectors/ post /api/asset discovery collectors put /api/asset discovery collectors/ delete /api/asset discovery collectors/ post /api/asset discovery collectors/trigger scan asset intelligence — base /api/asset intelligence método endpoint get /api/asset intelligence/list get /api/asset intelligence/{equipment +}/metrics history get /api/asset intelligence/{equipment +}/detail get /api/asset intelligence/{equipment +}/blast radius get /api/asset intelligence/{equipment +}/impact get /api/asset intelligence/{equipment +}/compromise get /api/asset intelligence/{equipment +}/insights asset relationship — base /api/asset relationships método endpoint get /api/asset relationships/search get /api/asset relationships/graph get /api/asset relationships/edges get /api/asset relationships get /api/asset relationships/catalog post /api/asset relationships put /api/asset relationships/ delete /api/asset relationships/ attack — base /api/attack método endpoint get /api/attack/taxonomy get /api/attack/coverage cmdb export — base /api/db/discovery/assets método endpoint get /api/db/discovery/assets/latest collector — base /api/collectors método endpoint get /api/collectors get /api/collectors/ get /api/collectors/ /config get /api/collectors/ /version post /api/collectors put /api/collectors/ delete /api/collectors/ config health — base /api/admin/config método endpoint get /api/admin/config/health post /api/admin/config/secrets/refresh connector — base /api/connectors método endpoint post /api/connectors/cloudtrail post /api/connectors/windows event correlation rule — base /api/correlation rules método endpoint get /api/correlation rules get /api/correlation rules/types get /api/correlation rules/ post /api/correlation rules put /api/correlation rules/ delete /api/correlation rules/ post /api/correlation rules/validate post /api/correlation rules/simulate get /api/correlation rules/effectiveness get /api/correlation rules/ /effectiveness get /api/correlation rules/ /effectiveness/history device — base /api/devices método endpoint get /api/devices get /api/devices/ put /api/devices/ /tags get /api/devices/tags/values device reconciliation — base /api/device reconciliation método endpoint get /api/device reconciliation post /api/device reconciliation/create device type — base /api/device types método endpoint get /api/device types get /api/device types/active get /api/device types/ post /api/device types put /api/device types/ delete /api/device types/ discard policy — base /api/discard policies método endpoint get /api/discard policies get /api/discard policies/active get /api/discard policies/ post /api/discard policies put /api/discard policies/ delete /api/discard policies/ post /api/discard policies/suggest post /api/discard policies/preview post /api/discard policies/apply suggestions post /api/discard policies/ /apply discovered pending — base /api/discovered pending método endpoint get /api/discovered pending post /api/discovered pending/ /incorporate discovery db — base /api/db/discovery método endpoint post /api/db/discovery get /api/db/discovery/health discovery device allowlist — base /api/discovery allowlist método endpoint get /api/discovery allowlist post /api/discovery allowlist delete /api/discovery allowlist/ effective config — base /api/admin/config método endpoint get /api/admin/config/effective event chat — base /api/events método endpoint get /api/events/ /chat post /api/events/ /chat delete /api/events/ /chat event closure — base /api/events método endpoint post /api/events/ /acknowledge post /api/events/ /start post /api/events/ /send to action post /api/events/ /close post /api/events/ /discard post /api/events/ /reopen get /api/events/ /timeline get /api/events/ /notifications post /api/events/ /notify post /api/events/bulk close post /api/events/bulk discard event — base /api/events método endpoint post /api/events/correlate post /api/events/analyze post /api/events/trigger llm post /api/events/search post /api/events/discard post /api/events/autonomous action event feedback — base /api/event feedback método endpoint post /api/event feedback get /api/event feedback/event/ get /api/event feedback event rule — base /api/event rules método endpoint get /api/event rules get /api/event rules/ post /api/event rules put /api/event rules/ delete /api/event rules/ post /api/event rules/sync from events event similarity — base /api/events método endpoint get /api/events/ /similar events dashboard — base /api/dashboard método endpoint get /api/dashboard/mttr get /api/dashboard/events hyper agent — base /api/hyper método endpoint get /api/hyper/config put /api/hyper/config post /api/hyper/challenge get /api/hyper/challenge/ post /api/hyper/board key get /api/hyper/companies get /api/hyper/companies/ /agents post /api/hyper/companies/ /issues get /api/hyper/event issues/ get /api/hyper/issues/ get /api/hyper/issues/ /runs get /api/hyper/issues/ /live runs get /api/hyper/heartbeat runs/ /events get /api/hyper/heartbeat runs/ /log get /api/hyper/issues/ /comments post /api/hyper/issues/ /comments post /api/hyper/agents/ /wake get /api/hyper/issues/ /approvals patch /api/hyper/companies/ /approvals/ incident dossier — base /api/events método endpoint get /api/events/ /dossier post /api/events/ /dossier/generate info — base /api/infos método endpoint get /api/infos/version known error — base /api/known errors método endpoint get /api/known errors post /api/known errors post /api/known errors/bulk put /api/known errors/ delete /api/known errors/ post /api/known errors/match/ liveness — base /api/liveness método endpoint get /api/liveness/assets get /api/liveness/services get /api/liveness/summary post /api/liveness/run log — base /api/logs método endpoint post /api/logs/search post /api/logs/analyze get /api/logs/dashboard get /api/logs/rules get /api/logs/templates get /api/logs/rulesmatch get /api/logs/users get /api/logs/levels get /api/logs/types get /api/logs/patterns post /api/logs/correlated counts get /api/logs/ post /api/logs/discard post /api/logs/discardbytemplate get /api/logs/timeline post /api/logs/analyze pattern post /api/logs/register manual menu layout — base /api/ui método endpoint get /api/ui/menu layout metric catalog — base /api/metrics/catalog método endpoint get /api/metrics/catalog put /api/metrics/catalog/ post /api/metrics/catalog/ /curate post /api/metrics/catalog/refresh post /api/metrics/catalog/scan metric — base /api/metrics método endpoint post /api/metrics/search post /api/metrics/timeseries post /api/metrics/insights post /api/metrics/forecast post /api/metrics/chat post /api/metrics/by equipment post /api/metrics/by equipment/insights get /api/metrics/equipments get /api/metrics/types get /api/metrics/levels get /api/metrics/rules get /api/metrics/statuses monitor — base /api/monitor método endpoint get /api/monitor/events get /api/monitor/events/ /timeline get /api/monitor/metrics/summary get /api/monitor/incidents/ /graph get /api/monitor/dictionaries/rules get /api/monitor/dictionaries/hostnames get /api/monitor/stream morning call — base /api/dashboard método endpoint get /api/dashboard/morning call network discovery — base /api/network discovery método endpoint get /api/network discovery/data get /api/network discovery/redundancy candidates get /api/network discovery/diff post /api/network discovery/criticality/recompute post /api/network discovery/threat summary post /api/network discovery/merge patch /api/network discovery/ /active network discovery health — base /api/network discovery método endpoint get /api/network discovery/health notification channel — base /api/notification channels método endpoint get /api/notification channels get /api/notification channels/ post /api/notification channels put /api/notification channels/ delete /api/notification channels/ post /api/notification channels/ /test post /api/notification channels/test central post /api/notification channels/preview central notification — base /api/notifications método endpoint get /api/notifications get /api/notifications/unread count post /api/notifications/ /read post /api/notifications/read all get /api/notifications/stream ocsf export — base /api/export/ocsf método endpoint get /api/export/ocsf/logs get /api/export/ocsf/events orchestration — base /api/orchestration método endpoint get /api/orchestration/health get /api/orchestration/me get /api/orchestration/companies get /api/orchestration/companies/ /issues post /api/orchestration/companies/ /issues get /api/orchestration/issues/ get /api/orchestration/companies/ /approvals post /api/orchestration/agents/ /heartbeat post /api/orchestration/approvals/ / pipeline — base /api/pipeline método endpoint get /api/pipeline/asset risk get /api/pipeline/health get /api/pipeline/stats get /api/pipeline/status get /api/pipeline/runs post /api/pipeline/trigger/ processing rule — base /api/processing rules método endpoint get /api/processing rules get /api/processing rules/ post /api/processing rules put /api/processing rules/ delete /api/processing rules/ prompt — base /api/prompts método endpoint get /api/prompts get /api/prompts/ put /api/prompts/ post /api/prompts/ /reset rca feedback — base /api/rca feedback método endpoint post /api/rca feedback get /api/rca feedback relationship map — base /api/relationship maps método endpoint get /api/relationship maps get /api/relationship maps/ post /api/relationship maps put /api/relationship maps/ delete /api/relationship maps/ reliability — base /api/reliability método endpoint get /api/reliability/services get /api/reliability/services/ get /api/reliability/services/ /forecast get /api/reliability/services/ /diagnosis get /api/reliability/whatif/cis post /api/reliability/whatif remediation — base /api/remediations método endpoint post /api/remediations/plan post /api/remediations/ /execute get /api/remediations/event/ retention — base /api/retention método endpoint get /api/retention post /api/retention put /api/retention/ delete /api/retention/ post /api/retention/ /apply get /api/retention/ /preview rule suggestion — base /api/rule suggestions método endpoint get /api/rule suggestions get /api/rule suggestions/ post /api/rule suggestions/ /approve post /api/rule suggestions/ /reject runtime config — base /api/admin/config/runtime método endpoint get /api/admin/config/runtime put /api/admin/config/runtime/ delete /api/admin/config/runtime/ saved view — base /api/saved views método endpoint get /api/saved views get /api/saved views/ post /api/saved views put /api/saved views/ delete /api/saved views/ security events — base /api/security events método endpoint post /api/security events/search get /api/security events/hosts get /api/security events/sources get /api/security events/event types get /api/security events/severities service command — base /api/command map método endpoint get /api/command map/services get /api/command map/ /graph get /api/command map/ /swimlanes get /api/command map/ /timeline get /api/command map/ /forecast get /api/command map/ /diagnosis post /api/command map/remediation service group — base /api/service groups método endpoint get /api/service groups get /api/service groups/ post /api/service groups post /api/service groups/suggest post /api/service groups/apply suggestions put /api/service groups/ delete /api/service groups/ post /api/service groups/resolve get /api/service groups/ /hostnames get /api/service groups/ /summary get /api/service groups/ /events get /api/service groups/ /blast radius get /api/service groups/ /chat post /api/service groups/ /chat delete /api/service groups/ /chat get /api/service groups/ /dossier post /api/service groups/ /dossier/generate service monitor — base (none método endpoint get /api/service monitor get /api/service monitor/ get /api/service monitor/ /timeline get /api/service monitor/ /situations get /api/service monitor/ /predictions get /api/service blueprints get /api/service blueprints/ post /api/service blueprints put /api/service blueprints/ delete /api/service blueprints/ get /api/service blueprints/ /preview post /api/service blueprints/ /apply sigma — base /api/sigma método endpoint post /api/sigma/preview post /api/sigma/import sla — base /api/sla método endpoint get /api/sla/rules post /api/sla/rules put /api/sla/rules/ delete /api/sla/rules/ get /api/sla/predictions get /api/sla/predictions/by equipment get /api/sla/predictions/by service threat indicator — base /api/threat indicators método endpoint get /api/threat indicators/search get /api/threat indicators/stats post /api/threat indicators/asset counts get /api/threat indicators/assets get /api/threat indicators/export csv get /api/threat indicators/export stix threat intel auto — base /api/threat intel/auto método endpoint get /api/threat intel/auto/status get /api/threat intel/auto/test connection get /api/threat intel/auto/cves post /api/threat intel/auto/import threat intel — base /api/threat intel método endpoint post /api/threat intel/fetch trace — base /api/traces método endpoint post /api/traces/search get /api/traces/by id/ get /api/traces/by id/ /tree post /api/traces/search/aggregate post /api/traces/search/operations post /api/traces/by id/ /analyze get /api/traces/by id/ /related events get /api/traces/by id/ /blast radius get /api/traces/by id/ /baseline get /api/traces/by id/ /similar get /api/traces/service flow get /api/traces/service flow/insight get /api/traces/service flow/edge get /api/traces/service flow/service get /api/traces/service flow/bottlenecks get /api/traces/service flow/dependency drift post /api/traces/admin/seed verification group — base /api/verification groups método endpoint get /api/verification groups get /api/verification groups/active get /api/verification groups/ post /api/verification groups put /api/verification groups/ delete /api/verification groups/ 3 5 api — autonomous assets backend responsável pelo inventário de ativos lógicos e pelo canal de comunicação com o agente de endpoint (bootstrap, enrollment, configuração, diagnóstico e ingestão de observações) agent bootstrap — base /api/inventory/agent config/bootstrap método endpoint get /api/inventory/agent config/bootstrap agent config — base /api/inventory/agent método endpoint get /api/inventory/agent/config agent config template — base /api/inventory/agent config/templates método endpoint get /api/inventory/agent config/templates post /api/inventory/agent config/templates put /api/inventory/agent config/templates/ delete /api/inventory/agent config/templates/ agent diagnostics — base /api/inventory/agent método endpoint post /api/inventory/agent/diagnostics agent enrollment — base /api/inventory/agent método endpoint post /api/inventory/agent/enroll agent fleet — base /api/inventory/agents método endpoint get /api/inventory/agents/defaults post /api/inventory/agents/defaults get /api/inventory/agents post /api/inventory/agents/ /disable post /api/inventory/agents/ /enable delete /api/inventory/agents/ post /api/inventory/agents/ /config get /api/inventory/agents/ /config get /api/inventory/agents/ /fim config post /api/inventory/agents/ /fim config get /api/inventory/agents/ /event config post /api/inventory/agents/ /event config get /api/inventory/agents/ /registry config post /api/inventory/agents/ /registry config get /api/inventory/agents/ /runtime config post /api/inventory/agents/ /runtime config agent ingestion — base /api/inventory/agent método endpoint post /api/inventory/agent/observations agent release — base /api/inventory/agent método endpoint get /api/inventory/agent/version post /api/inventory/agent/releases agent telemetry — base /api/inventory método endpoint post /api/inventory/agent/telemetry get /api/inventory/assets/ /telemetry agentless ca cert — base /api/inventory/agentless/ca certs método endpoint get /api/inventory/agentless/ca certs post /api/inventory/agentless/ca certs delete /api/inventory/agentless/ca certs/ agentless credential — base /api/inventory/agentless/credentials método endpoint get /api/inventory/agentless/credentials post /api/inventory/agentless/credentials put /api/inventory/agentless/credentials/ delete /api/inventory/agentless/credentials/ agentless execution — base /api/inventory/agentless/profiles método endpoint post /api/inventory/agentless/profiles/ /run agentless run — base /api/inventory/agentless/runs método endpoint get /api/inventory/agentless/runs asset ai — base /api/inventory/insights método endpoint post /api/inventory/insights/ask asset — base /api/inventory/assets método endpoint get /api/inventory/assets get /api/inventory/assets/facets get /api/inventory/assets/ asset management — base /api/inventory/assets/ método endpoint get /api/inventory/assets/ /costs post /api/inventory/assets/ /costs delete /api/inventory/assets/ /costs/ patch /api/inventory/assets/ /management delete /api/inventory/assets/ post /api/inventory/assets/ /restore patch /api/inventory/assets/ /attributes post /api/inventory/assets/ /lifecycle post /api/inventory/assets/ /lifecycle state post /api/inventory/assets/ /tags delete /api/inventory/assets/ /tags/ post /api/inventory/assets/ /global tags/ delete /api/inventory/assets/ /global tags/ get /api/inventory/assets/ /history asset relationship proxy — base /api/inventory/relationships método endpoint get /api/inventory/relationships/catalog get /api/inventory/relationships/search get /api/inventory/relationships/graph get /api/inventory/relationships/edges get /api/inventory/relationships/service groups get /api/inventory/relationships/maps get /api/inventory/relationships/maps/ post /api/inventory/relationships/maps put /api/inventory/relationships/maps/ delete /api/inventory/relationships/maps/ post /api/inventory/relationships put /api/inventory/relationships/ delete /api/inventory/relationships/ audit — base /api/inventory/audit método endpoint get /api/inventory/audit get /api/inventory/audit/export blacklist — base /api/inventory/blacklist método endpoint get /api/inventory/blacklist post /api/inventory/blacklist delete /api/inventory/blacklist/ certificate — base /api/inventory/certificates método endpoint get /api/inventory/certificates get /api/inventory/certificates/expiring post /api/inventory/certificates put /api/inventory/certificates/ delete /api/inventory/certificates/ post /api/inventory/certificates/import get /api/inventory/certificates/ /file collection profile — base /api/inventory/agentless/profiles método endpoint get /api/inventory/agentless/profiles post /api/inventory/agentless/profiles put /api/inventory/agentless/profiles/ delete /api/inventory/agentless/profiles/ conformance — base /api/inventory/conformance método endpoint get /api/inventory/conformance get /api/inventory/conformance/summary post /api/inventory/conformance/run contract — base /api/inventory/contracts método endpoint get /api/inventory/contracts post /api/inventory/contracts put /api/inventory/contracts/ delete /api/inventory/contracts/ discovered pending — base /api/inventory/discovered método endpoint get /api/inventory/discovered/pending post /api/inventory/discovered/ /incorporate export — base /api/inventory/export método endpoint get /api/inventory/export get /api/inventory/export/compliance field definition — base /api/inventory/field definitions método endpoint get /api/inventory/field definitions post /api/inventory/field definitions patch /api/inventory/field definitions/ delete /api/inventory/field definitions/ fim — base /api/inventory/fim método endpoint get /api/inventory/fim/events get /api/inventory/fim/summary post /api/inventory/fim/events/ /approve fim template — base /api/inventory/fim/templates método endpoint get /api/inventory/fim/templates post /api/inventory/fim/templates put /api/inventory/fim/templates/ delete /api/inventory/fim/templates/ financial report — base /api/inventory/financial método endpoint get /api/inventory/financial form layout — base /api/inventory/form layouts método endpoint get /api/inventory/form layouts/ put /api/inventory/form layouts/ info — base /api/inventory método endpoint get /api/inventory/info insights — base /api/inventory/insights método endpoint get /api/inventory/insights inventory alert rule — base /api/inventory/alert rules método endpoint get /api/inventory/alert rules get /api/inventory/alert rules/types post /api/inventory/alert rules put /api/inventory/alert rules/ delete /api/inventory/alert rules/ inventory change — base /api/inventory método endpoint get /api/inventory/assets/ /changes get /api/inventory/changes inventory trend — base /api/inventory/trends método endpoint get /api/inventory/trends post /api/inventory/trends/snapshot license assignment — base /api/inventory/license assignments método endpoint get /api/inventory/license assignments/ post /api/inventory/license assignments post /api/inventory/license assignments/ /revoke license — base /api/inventory método endpoint get /api/inventory/licenses get /api/inventory/compliance get /api/inventory/compliance/summary get /api/inventory/compliance/issues get /api/inventory/licenses/ post /api/inventory/licenses patch /api/inventory/licenses/ delete /api/inventory/licenses/ post /api/inventory/licenses/import license panel — base /api/inventory/license panel método endpoint get /api/inventory/license panel license utilization — base /api/inventory/utilization método endpoint get /api/inventory/utilization lifecycle state — base /api/inventory/lifecycle states método endpoint get /api/inventory/lifecycle states post /api/inventory/lifecycle states put /api/inventory/lifecycle states/ delete /api/inventory/lifecycle states/ metrics — base /api/inventory/metrics método endpoint get /api/inventory/metrics/overview get /api/inventory/metrics/distribution normalization — base /api/inventory/normalization método endpoint get /api/inventory/normalization/rules post /api/inventory/normalization/rules delete /api/inventory/normalization/rules/ get /api/inventory/normalization/suites post /api/inventory/normalization/suites put /api/inventory/normalization/suites/ delete /api/inventory/normalization/suites/ post /api/inventory/normalization/suites/ /members delete /api/inventory/normalization/suites/members/ org unit — base /api/inventory/org units método endpoint get /api/inventory/org units post /api/inventory/org units put /api/inventory/org units/ delete /api/inventory/org units/ publisher — base /api/inventory/publishers método endpoint get /api/inventory/publishers get /api/inventory/publishers/lifecycle get /api/inventory/publishers/products post /api/inventory/publishers put /api/inventory/publishers/ delete /api/inventory/publishers/ put /api/inventory/publishers/products/ registry template — base /api/inventory/registry/templates método endpoint get /api/inventory/registry/templates post /api/inventory/registry/templates put /api/inventory/registry/templates/ delete /api/inventory/registry/templates/ report export — base /api/inventory/reports método endpoint get /api/inventory/reports/ software — base /api/inventory método endpoint get /api/inventory/assets/ /software get /api/inventory/software get /api/inventory/software/ get /api/inventory/software/unmatched post /api/inventory/software patch /api/inventory/software/ post /api/inventory/software/aliases tag — base /api/inventory/tags método endpoint get /api/inventory/tags post /api/inventory/tags patch /api/inventory/tags/ delete /api/inventory/tags/ vendor license rule — base /api/inventory/license rules método endpoint get /api/inventory/license rules get /api/inventory/license rules/ /required vulnerability — base /api/inventory/vulnerabilities método endpoint get /api/inventory/vulnerabilities get /api/inventory/vulnerabilities/summary get /api/inventory/vulnerabilities/findings get /api/inventory/vulnerabilities/asset/ post /api/inventory/vulnerabilities/ingest post /api/inventory/vulnerabilities/scan post /api/inventory/vulnerabilities/findings/ /status 3 6 api — autonomous discovery backend responsável pela descoberta ativa de ativos em rede a partir do serviço de scan discovery — base /api/discovery método endpoint post /api/discovery/scan 3 7 api — autonomous pipeline backend da esteira de dados, expõe endpoints de status, execução manual de jobs e disparo de sincronizações pipeline — base /api/v1/pipeline método endpoint get /api/v1/pipeline/status get /api/v1/pipeline/runs post /api/v1/pipeline/maintenance/reconcile run get /api/v1/pipeline/sync log post /api/v1/pipeline/trigger/incremental post /api/v1/pipeline/trigger/full sync post /api/v1/pipeline/trigger/enrichment post /api/v1/pipeline/trigger/center asset sync post /api/v1/pipeline/trigger/center software sync post /api/v1/pipeline/trigger/agent inventory sync post /api/v1/pipeline/trigger/nvd backfill post /api/v1/pipeline/trigger/wazuh inventory sync post /api/v1/pipeline/trigger/wazuh vuln sync post /api/v1/pipeline/trigger/wazuh alerts mitre sync post /api/v1/pipeline/trigger/matching post /api/v1/pipeline/trigger/suggest aliases post /api/v1/pipeline/trigger/appliance smoke post /api/v1/pipeline/trigger/promote llm suggestions post /api/v1/pipeline/trigger/llm resolve aliases post /api/v1/pipeline/trigger/embed suggest aliases post /api/v1/pipeline/trigger/regex suggest aliases post /api/v1/pipeline/trigger/promote suggestions post /api/v1/pipeline/trigger/risk cycle post /api/v1/pipeline/trigger/alias discovery post /api/v1/pipeline/trigger/reclassify unmatchable post /api/v1/pipeline/trigger/countermeasure heartbeat post /api/v1/pipeline/trigger/countermeasure heartbeat/ post /api/v1/pipeline/trigger/dedup scan post /api/v1/pipeline/trigger/dynamic risk post /api/v1/pipeline/trigger/operational risk post /api/v1/pipeline/trigger/compromise level post /api/v1/pipeline/trigger/propagate hierarchy post /api/v1/pipeline/trigger/compromise decay post /api/v1/pipeline/trigger/cmdb sync post /api/v1/pipeline/trigger/asset quality post /api/v1/pipeline/trigger/security sync post /api/v1/pipeline/trigger/security link assets post /api/v1/pipeline/trigger/bootstrap post /api/v1/pipeline/trigger/replay get /api/v1/pipeline/stats validações e tratamento de erros 4 1 validação de dados todas as requisições ao autonomous center passam por um handler central de exceções (apiexceptionhandler) payloads com bean validation (@valid) são checados antes do processamento, e parâmetros de query/path são validados quanto ao tipo e à obrigatoriedade em caso de violação, o serviço retorna 400 bad request com o detalhamento dos campos inválidos, sem expor stacktrace 4 2 formato padrão da resposta de erro as respostas de erro retornam um corpo json consistente { "status" 400, "error" "validação falhou", "fields" { "nomedocampo" "mensagem de erro específica do campo" } } o campo fields é incluído apenas quando há violações de validação por campo em erros gerais (ex parâmetro inválido, transição de estado bloqueada), apenas status e error são retornados 4 3 códigos http utilizados código significado quando ocorre 400 bad request validação de payload falhou; parâmetro obrigatório ausente; tipo de parâmetro inválido; argumento fora do domínio esperado 401 unauthorized token jwt ausente ou inválido (quando app security enabled=true) 403 forbidden token válido, porém sem o escopo ou role exigido pela rota (por exemplo, rota sob /api/admin/ sem role config admin) 404 not found recurso identificado por id não encontrado 409 conflict conflito de concorrência otimista (objectoptimisticlockingfailureexception); transição de estado de evento não permitida; conflito cas no opensearch (eventconflictexception) 422 unprocessable entity regra de negócio recusa o payload após validação sintática 500 internal server error falha não tratada o erro é logado internamente; a resposta ao cliente traz apenas a mensagem "erro interno " (sem stacktrace) 4 4 exemplo de resposta de erro por tipo validação de campo (400) { "status" 400, "error" "validação falhou", "fields" { "nome" "não pode ser vazio" } } parâmetro inválido em query/path (400) { "status" 400, "error" "parâmetro inválido 'days' " } parâmetro obrigatório ausente (400) { "status" 400, "error" "parâmetro obrigatório ausente 'ruleid' " } conflito de concorrência otimista (409) { "status" 409, "error" "conflito de concorrência o registro foi alterado por outra operação recarregue e tente de novo " } erro interno (500) { "status" 500, "error" "erro interno " } observações e limites do documento cabeçalhos de headers personalizados, contratos detalhados de request/response (schemas de dto), exemplos completos de payload por endpoint e códigos de erro específicos de cada rota não estão descritos nesta versão a rotina de extração cobriu método http, caminho e agrupamento por controlador, que é a informação diretamente obtida do código fonte endpoints marcados como administrativos (sob /api/admin/ ) e o par /api/collectors/ /config e /api/collectors/ /version possuem restrições de autorização adicionais (ver seção 3 3) consumo por integradores externos deve ser previamente autorizado pela equipe de operação do autonomous o serviço autonomous collector, presente na stack, atua predominantemente como processador de eventos e integração com fontes externas; não expõe uma api rest pública com controladores no mesmo padrão dos demais serviços listados o agente de endpoint (autonomous agent) é um cliente da api do autonomous assets, sem exposição de rotas http próprias a relação de rotas foi extraída a partir das anotações @getmapping, @postmapping, @putmapping, @deletemapping, @patchmapping e @requestmapping presentes nos controllers do backend endpoints registrados dinamicamente em tempo de execução (não anotados) não fazem parte desta relação suporte dúvidas técnicas sobre integração devem ser encaminhadas à equipe de tecnologia da central it, responsável pela stack autonomous solicitações de expansão deste documento (schemas detalhados, exemplos por endpoint, documentação openapi/swagger publicada) devem ser abertas via o processo padrão de demandas técnicas do produto