Enterprise integration
GuardRoute.ai
Integration guide
Policy controls before sensitive actions execute. Use the customer portal to coordinate onboarding and manage credentials for your organization.
Your product endpoint
Use this address after your organization receives production access and integration approval. API calls require a product-specific credential and verified subscription access.
POST https://guardroute.ai/api/v1/products/guardroute/evaluate
Authorization: Bearer <your product API key>
Content-Type: application/jsonEvaluate a proposed action
{
"action": "transfer",
"destination": "your-approved-destination-id",
"amountMinor": 10000,
"currency": "USD"
}Example only. Action names and destination identifiers must match your configured policy. Amounts are non-negative integers in the currency’s minor units. Supply all four fields; additional fields are rejected. Policy is maintained by your authorized onboarding team and cannot be overridden by an API caller.
Handle every outcome
Responses contain requestId, product, decision, reason, policyVersion and executionPerformed: false. Your system must enforce the decision.
| Decision | Your application |
|---|---|
| allow | May continue within the approved workflow. |
| approval_required | Wait for the required approval. |
| escalate | Route to the designated reviewer. |
| hold | Pause until the hold is resolved. |
| block | Do not execute the action. |
Hold an action for review on a timeout, error, unknown decision or unavailable service. GuardRoute does not execute payments or custody funds.
Credentials and request limits
Keep keys in your server-side secrets manager. Send them only in the Authorization header, never in a URL or browser code. Keys expire after 90 days and can be revoked through Customer access once credential management is activated.
The initial operational limit is 60 requests per minute per key with a maximum 16 KB request body. These are technical limits, not subscription allowances.
- 400
- Invalid request
- 401
- Missing or invalid API key
- 403
- Subscription access unavailable
- 413
- Request body too large
- 429
- Rate limit reached
- 503
- Service or integration unavailable
Do not retry rejected actions automatically. For 429 responses, use bounded backoff; for 503 responses, confirm service availability with support.