WayloAIWaylo Docs
APIReferenceProvider keys

Update key settings

PUT
/provider-keys/settings

Set what a stage does when the tenant’s key fails or is known bad. strict never runs that provider on the platform key; failover does.

Access: tenant_admin · API key provider_keys:write

Authorization

api-key
headerAuthorizationBearer <sk_waylo_<lookup><secret><checksum>>

Header Parameters

Authorization*string

Your API key.

Request Body

application/json
  1. body
failureMode*string
Value in"strict""failover"

Response Body

Updated

application/json
  1. response
failureMode*string
Value in"strict""failover"
Example Request
curl -X PUT 'https://api.poc.app.waylovoice.ai/provider-keys/settings' \  -H 'Authorization: Bearer sk_waylo_...' \  -H 'Content-Type: application/json' \  -d '{  "failureMode": "strict"}'
Example Response
{  "failureMode": "strict"}

Set provider key PUT

Add or replace the tenant’s key for a provider. The key is checked against the provider and stored whatever the answer, with the result in `status`: a key that fails the check is flagged, not refused. 503 when credential encryption is not configured. **Access:** tenant_admin · API key `provider_keys:write`

Validate provider key POST

Check the stored key against the provider again, after fixing the account. A pass sets `valid`; the next failed call sets the status again. A check that cannot reach the provider changes nothing. `check` is what the provider answered: `unverified` when the check proved nothing, null when the key was replaced while it ran. **Access:** tenant_admin · API key `provider_keys:write`