Accept terms of service
Records acceptance of the terms a capability requires, by submitting the signed agreement id the user obtained from the provider’s hosted flow.
The agreementId is opaque — the platform resolves which provider it belongs to from the user’s outstanding terms_acceptance requirement. Callers never need to know the provider.
While the requirement is outstanding, the user’s capabilities carry a terms_acceptance requirement whose actionUrl is the hosted flow that produces this id.
Authorizations
Cognito JWT token for regular user authentication
Body
Terms acceptance for the authenticated user.
Terms acceptance for the authenticated user.
The signed agreement id the user received from the provider's hosted terms flow (surfaced via the terms_acceptance requirement's actionUrl). Opaque — the platform resolves which provider it belongs to.
1Optional fraud-session id from the provider's client SDK (e.g. a Radar session), forwarded to the provider for fraud checks.
1Response
Result of a terms acceptance.
Result of a terms acceptance.
Whether the agreement was recorded and terms are now accepted.