Delete a trust rule
⚠️
Preview — this feature is being built; the design below is the spec.
DELETE https://app.syntic.ai/v1/organizations/service_accounts/{service_account_id}/trust_rules/{rule_id}Delete a rule. New exchanges that only this rule matched fail with invalid_grant from now on.
For how this fits into a full workflow, see Workload identity.
Headers
| Header | Required | Value |
|---|---|---|
Authorization | Yes | Bearer <admin key>: an Admin API key (sk_admin_...). Inference keys are refused with 403 admin_key_required. See Admin API keys. |
syntic-beta | Yes, while in preview | admin-2026-11-01. Without it the call fails with 400 beta_required. See Versioning. |
Path parameters
| Parameter | Type | Description |
|---|---|---|
service_account_id | string | The service account id, starting with svcacct_. |
rule_id | string | The rule id, starting with frule_. |
Response
200 OK, Content-Type: application/json
{
"id": "frule_01JCK9M1P3R5T7V9X1Z3",
"type": "trust_rule",
"deleted": true
}Examples
curl -sS -X DELETE "https://app.syntic.ai/v1/organizations/service_accounts/svcacct_01JCH7K9M1P3R5T7V9X1/trust_rules/frule_01JCK9M1P3R5T7V9X1Z3" \
-H "Authorization: Bearer $SYNTIC_ADMIN_KEY" \
-H "syntic-beta: admin-2026-11-01"Errors
Errors use the error envelope and carry a request_id. Codes specific to this operation:
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request_error | beta_required | The syntic-beta header is missing. |
| 404 | not_found_error | trust_rule_not_found | No rule with this id on the service account. |
| 401 | authentication_error | invalid_api_key | The admin key is missing, unknown, revoked or expired. |
| 403 | permission_error | admin_key_required | An inference key was used. |
| 429 | rate_limit_error | rate_limited | Too many requests; wait for Retry-After. See Rate-limit headers. |
Was this page helpful?