Expand description
hosted/* protocol DTOs (roadmap phase 72, Task 1).
Contract-first: these DTOs and the method manifest entries define the hosted multi-tenant surface before the gateway implementation lands (phase 72 Task 2). Tenant identity is always resolved server-side from validated credentials — no request DTO here accepts a caller-supplied tenant id for core operations.
Structs§
- Hook
Delivery - One delivery attempt lifecycle for a matched event.
- Hook
Retry Policy - Retry policy for failed deliveries (bounded exponential backoff).
- Hosted
Audit List Params - Hosted
Audit List Result - Hosted
Audit Record - A redaction-safe audit row: coarse action, actor/tenant context, and an outcome — never request bodies or credentials.
- Hosted
Hook Create Params - Hosted
Hook Definition - Hosted
Hook Delete Params - Hosted
Hook Result - Hosted
Hook Update Params - Hosted
Hooks List Result - Hosted
Request Context - Fully resolved request identity, attached by the hosted gateway before dispatch. Local mode never builds one.
- Hosted
Service Account Create Params - Hosted
Service Account Create Result - The API key secret appears exactly once, in this response; the server stores only its hash.
- Hosted
Service Account Revoke Params - Hosted
Service Account Revoke Result - Hosted
Service Account Summary - Hosted
Service Accounts List Result - Hosted
Tenant Read Params - Hosted
Tenant Read Result - Hosted
Tenants List Result - Hosted
Usage Read Params - Hosted
Usage Read Result - Hosted
Whoami Result hosted/whoami— the resolved identity of the calling credential.- Tenant
Context
Enums§
- Hook
Delivery Status - Hook
Scope - Hosted
Role - Tenant-level role of a principal.
- Hosted
Scope - Coarse hosted access scopes attached to a credential.
- Principal
Context - Who is acting: a human user or a service account. Credential material (tokens, key hashes) never appears here.