Skip to content

Developer portal

POST /tenant/integrations/{provider}

Configure read-only cloud CBOM pull for AWS ACM or Azure Key Vault.

PilotPOST /tenant/integrations/{provider}Auth: API key required

Summary

Configure read-only cloud CBOM pull for AWS ACM or Azure Key Vault.

Example

curl

curl -X POST "https://sparkling-vibrancy-production-1a7a.up.railway.app/tenant/integrations/{provider}" \
  -H "Authorization: Bearer 811f31d4-5b8e-4ed0-a7a2-8176e05eba63" \
  -H "Content-Type: application/json" \
  -d '{
  "region": "us-east-1",
  "roleArn": "arn:aws:iam::123456789012:role/QtanglReadOnly"
}'

Request body

FieldTypeRequiredDescription
regionstringNo

AWS region (provider=aws).

roleArnstringNo

Cross-account IAM role ARN (aws).

vaultNamestringNo

Azure Key Vault name (azure).

Errors

CodeMeaningTypical causeSuggested fix
400Bad requestMalformed JSON or missing required headers.Validate Content-Type and JSON syntax before retrying.
401UnauthorizedMissing or invalid API key in Authorization, x-api-key, or query param.Send Bearer <key> or x-api-key with a valid tenant token.
402Payment requiredFeature not included in current entitlements (e.g. Monitor schedules, remediation automate).Upgrade via billing portal or contact sales for enterprise tier.
403ForbiddenValid key but insufficient role (viewer attempting write) or wrong admin key.Use operator or admin role key; check RBAC matrix.
404Not foundScan, schedule, share link, or resource id does not exist or expired.Verify id and tenant scope; share links expire per expiresHours.
413Payload too largeCBOM ingest or upload exceeds size limit.Split large CBOM documents or use cloud pull integration.
422Unprocessable entityInvalid payload shape, unsupported scenario, or infeasible constraints.Fix field errors in response detail; relax constraints and retry.
429Too many requestsPer-key rate limit exceeded (default 300 requests per minute) or public endpoint limit.Backoff with jitter; cache results; request higher limit for production.
500Internal server errorUnexpected backend failure; includes requestId in response.Retry with exponential backoff; contact support with requestId if persistent.
503Service unavailablePersistence disabled, auth DB unreachable, or admin API not configured.Retry shortly; schedules require Postgres persistence enabled.
501Not implementedProblem type not yet supported on live solver path (routing, allocation).Use type schedule for live jobs, or follow Labs roadmap.

See the full errors reference.