What a waiting grant could be for

POST

/auth/zoho/connect/options

curl --request POST \
  --url https://api.sloose.com/auth/zoho/connect/options \
  --header 'Content-Type: application/json' \
  --data '{ "nonce": "example" }'

• Production
• Staging

The two organisations Zoho answered for, when both of its hosts did and the person has to say which they chose on Zoho’s screen — for the app’s page that asks (/connect/choose). nonce is the one the connect callback handed that page; it is read here and not spent, and the answer goes to POST /auth/zoho/connect/choose.

You never call this directly.

Request Body^required

Media typeapplication/json

object

nonce

required

string

>= 1 characters <= 200 characters

Example^generated

{
  "nonce": "example"
}

Responses

200

What Zoho reported, per host.

Media typeapplication/json

object

options

required

Array<object>

object

host

required

string

Allowed values: standard sandbox

companyName

required

string | null

externalId

required

string

Example

{
  "options": [
    {
      "host": "standard"
    }
  ]
}

400

The request — its body or its query — did not match the schema. issues carries the Zod issue list.

Media typeapplication/json

The error envelope every non-2xx answer uses.

object

error

required

Human-readable explanation.

string

code

Machine-readable reason. Absent on a few legacy 400s.

string

key

additional properties

Example^generated

{
  "error": "example",
  "code": "example"
}

404

No choice waits under that nonce: it expired, or was made (code: CHOICE_GONE).

Media typeapplication/json

The error envelope every non-2xx answer uses.

object

error

required

Human-readable explanation.

string

code

Machine-readable reason. Absent on a few legacy 400s.

string

key

additional properties

Example^generated

{
  "error": "example",
  "code": "example"
}