POST /setup/assistant/check_ready_status

[vaguerant]

I'm not sure what exactly triggers this; currently I'm playing music from Spotify and I allowed the Android Home app to sleep, and this seems to trigger on wake each time. Not sure if Spotify is necessary or related in that regard. Also, the phone I'm using does not currently have its account linked to the Home.

Headers

Content-Type:application/json

Body

{
  "play_ready_message":false,
  "user_id":"?????????????????????"
}

"user_id" is a 21 digit decimal number, I'm not sure if it's something I should post publicly, so I won't. Anyway, here's the HTTP response to the above POST:

HTTP/1.1 200 OK
Access-Control-Allow-Headers: Content-Type
Cache-Control: no-cache
Access-Control-Allow-Origin: https://www.google.com
Content-Length: 108
Content-Type: application/json

{"can_enroll":true,"enrollment_state":0,"error":"NOT_LINKED","error_code":0,"ready":false,"retryable":false}

Anyway, if you set "play_ready_message" to true, Assistant gives the following (verbal) response:

Hi, I'm your Google Assistant. I'm here to help. To learn a few things you can do, continue in the Google Home app.

And the response:

{"can_enroll":true,"enrollment_state":0,"error_code":0,"ready":true}

[rithvikvibhu]

Which category would this go under?

[vaguerant]

Hmm, tough one, I guess it's sort of more of a Device Info function than an Assistant task. It seems to be related to initial setup/account linking, which isn't really an Assistant feature.