Replace asset_key_scopes on a CI binding
Mutate asset_key_scopes on the binding — gates the spec.assets slice for CI sessions. v1.48 introduced per-binding asset_key_scopes to lock down CI access to the assets slice, but POST /ci/v1/bindings doesn't accept the parameter, so existing bindings default to NULL (closed). This endpoint lets the binding owner (a principal with ci.manage on the project's owning org, same model as revoke) replace the scopes after the fact. Idempotent — calling with the same scope list is a no-op. Each scope is either an exact key (astro/hero.jpg) or a wildcard prefix (astro/*). Wildcards are required for assets.sync.prune to cover the prefix. Bare * and ** are rejected. Cap of 64 entries, 256 chars each, no empty strings.
Request
- Base URL: https://api.run402.com
- URL: https://api.run402.com/ci/v1/bindings/{binding_id}/asset-scopes
- Auth: API key in header SIGN-IN-WITH-X
Path parameters
Headers
SIWX auth header — base64-encoded JSON payload containing a signed CAIP-122 (EIP-4361) message. See https://docs.x402.org/extensions/sign-in-with-x.
Request body
Response
Binding updated. Returns the binding row including the new asset_key_scopes.
Changes
No recorded changes to this operation across all 1 revision of this API.