Say which organisation a grant was for
const url = 'https://api.sloose.com/auth/zoho/connect/choose';const options = { method: 'POST', headers: {'Content-Type': 'application/x-www-form-urlencoded'}, body: new URLSearchParams({nonce: 'example', host: 'standard'})};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.sloose.com/auth/zoho/connect/choose \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data nonce=example \ --data host=standardThe form on the page the connect callback shows when both of Zoho’s hosts answered for a new grant, and so nothing says which organisation the person picked on Zoho’s screen. nonce names the waiting grant — one use, ten minutes, stored hashed — and host is the answer. The grant then completes exactly as the callback would have: with the popup page inside a CRM tab, or back to the page it started on outside one.
You never call this directly.
Request Bodyrequired
Section titled “Request Bodyrequired”object
Which host the person chose, or cancel: nothing is connected, the waiting grant is revoked at Zoho, and the page the connect began on is told so (#730).
Responses
Section titled “Responses”A small HTML page that posts the outcome to window.opener and closes itself. Not a JSON API.
Started outside a CRM tab: back to the page it began on, with ?connected=<id> or ?connect_error=<why>.
A small HTML page that posts the outcome to window.opener and closes itself. Not a JSON API.
A small HTML page that posts the outcome to window.opener and closes itself. Not a JSON API.
A small HTML page that posts the outcome to window.opener and closes itself. Not a JSON API.
A small HTML page that posts the outcome to window.opener and closes itself. Not a JSON API.