Grant Access Scope
Attaches one or more scopes to an existing apiKey. A scope is the
service.scope pair declared by each Guper service in its account
configuration.
Today every service exposes a single all scope — register.all,
loyalty.all, order.all, sender.all, catalog.all,
organization.all, journey.all, media-manager.all,
auditObserver.all, pipeline.all, gapp-be.all — and connect
exposes six finer ones: connect.user, connect.access, connect.scope,
connect.session, connect.auth and connect.mcp. Finer scopes for the
other services are added as the need appears.
A request whose token belongs to a key without the scope the route
requires is refused with 403 and the response names the missing scope in
requiredScope. Calls signed between Guper services do not go through
this check.
Sent scopes that don't match a known service.scope come back in
invalidScopes; duplicate grants are silently ignored. The response
always reflects what was actually persisted.
Try-it values populated from environment ACME (Demo)
Authentication
Token
Most Connect endpoints require a valid x-guper-authorization token.
Token issuance itself (/api/connect/auth) is the exception — it
uses the x-guper-apikey and x-guper-apisecret credentials.
Headers
Request body
Content-Type:
application/json