data exchange

Returns the data exchange approval page for a short-lived token. The page renders in a browser. First, the app must create a token with POST /data-exchange/token. Then the app opens this URL in the browser of the user, with the token and app context. On the page, the user reviews the requested permissions. Then the user approves or cancels the exchange.

Approval is a one-time experience. If the user approved these permissions in an earlier exchange, this request does not render the page. The system consumes the token and redirects to the app callback with data_exchange_status=granted. This completes the exchange. The app must accept a granted callback from this URL without a second form submit.

Completes the browser approval flow. Redirects the browser to the configured callback URL of the app. When the user approves, the callback receives data_exchange_status=granted and granted_permissions. When the user cancels on the approval page, the callback receives data_exchange_status=cancelled, denied_permissions, and error=access_denied. After a recoverable error, if the system knows a safe callback, it redirects with data_exchange_status=error, error, and error_description.

Creates a short-lived token. The app passes the token to the /data-exchange browser flow as a query parameter. Send requested_permissions in the request body. It declares which permissions the user must review during the browser flow.

Tokens expire after five minutes. Each token is single-use. The system consumes a token when the user submits the form. The system also consumes a token when GET /data-exchange skips the approval page, because the user already approved the requested permissions. Create a new token for each exchange.