Hand the cloud browser sign in to a new popup

Server URLloading...

POST

/connections/{id}/browser:resume

Send

Authorization

Path

Body

Customer present only. The customer left the popup to read a code in their mail app and the phone threw it away, or closed the window by mistake, while the session still waits on them. This hands the SAME session (the same remote browser, still on the provider's page) to a new popup: the answer is the one of browser:start, with a new single use bootstrap code in the popup's address, and the previous popup's session token stops working at once. One popup at a time.

Allowed only while the session waits on the customer: about to sign in, signing in (a code prompt included), or while the agent has handed the page back. It takes the gate of browser:start (an end user's widget token bound to the domain and the end user, or the console, and an Origin on the return origin allowlist). A session takes a few, one every few seconds.

Path Parameters

Response Body

curl -X POST "https://example.com/connections/string/browser:resume" \  -H "Content-Type: application/json" \  -d '{}'

{  "session_id": "string",  "open_url": "http://example.com",  "vendor": "string",  "expires_at": "2019-08-24T14:15:22Z"}

{  "code": "string",  "title": "string",  "details": "string"}

{  "code": "string",  "title": "string",  "details": "string"}

{  "code": "string",  "title": "string",  "details": "string"}

{  "code": "string",  "title": "string",  "details": "string"}

{  "code": "string",  "title": "string",  "details": "string"}

{  "code": "string",  "title": "string",  "details": "string"}

{  "code": "string",  "title": "string",  "details": "string"}

{  "code": "string",  "title": "string",  "details": "string"}