assistant.conversations.current

The conversation to resume

GET/assistant/conversations/current

Operation: assistant.conversations.current
MCP tool: not exposed over MCP

This account's most recently used open conversation with the support assistant, or null when there is none. The panel calls it on open so a customer who closed the tab mid-question comes back to their thread rather than to an empty box. It never creates one: a conversation exists because a question was asked.

curl -X GET "https://api.gogoscreen.com/api/v1/assistant/conversations/current" \
  -H "Authorization: Bearer $GOGOSCREEN_API_KEY"

The shape of a request to this operation. The dashboard sends it with the signed in person's session; an API key is refused.

At a glance

Fact	Detail
Scopes	`assistant:use`
Credentials	a signed in dashboard session. An API key cannot be granted these scopes, so this operation is reachable only from a signed in dashboard session.
Rate limit	600 requests a minute per credential, in the `read` class.
Idempotency	Not applicable. This operation changes nothing.
MCP tool	Not exposed over MCP.
Always sets	`Cache-Control: private, no-store`

Response

Answers 200. Every answer also carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset, and every error body carries a requestId.

200 OK

The conversation to resume

200 OK body
Name	Type	Description
conversation	object \| null
createdAt	string	format: date-time
id	string	The conversation's id. Pass it as `conversationId` to keep asking in the same thread.
lastMessageAt	string \| null	When the thread was last written to. Null on a conversation with no messages yet.format: date-time
messageCount	integer	How many questions the customer has asked in this thread. The per-conversation cap counts this, not the replies.-9007199254740991–9007199254740991
status	string	`open` takes another question. `closed` and `handed_off` both refuse one with 409 `conversation_closed`; start a new conversation.one of: open, closed, handed_off

200 OK headers
Header	Meaning
`Cache-Control`	Always `private, no-store`.

Errors

Every refusal is { error: { code, message, details?, requestId } }. Branch on code, never on the sentence. The full catalogue is at Errors.

Code	Status	When it happens	What to do
validation_failed	400	The merged path, query and body did not match the operation's schema. The schemas are strict, so an unknown field is a failure rather than something ignored, and a string carrying half of a character is refused before it can be stored.	Read `details.issues`. Each entry carries a `path`, a `message` and a machine readable `code`. Fix every named field and send the request again; the same body always fails the same way.
unauthorized	401	No credential was presented, or the key is unknown, revoked or expired, or an `X-API-Key` header carried something that is not an API key. `details.reason` says which.	Send `Authorization: Bearer gsk_live_…`. A revoked or expired key never starts working again, so issue a new one in the developer console. Put a dashboard session token in `Authorization`, never in `X-API-Key`.
feature_disabled	403	The operation sits behind a feature flag this deployment has switched off.	Nothing a caller can change. Stop calling the operation, or ask the operator to enable it.
forbidden_scope	403	The credential does not carry every scope the operation declares, or it is the wrong kind of credential for it. `keys.` and `assistant.` are user only and can never be called by a key.	`details.requiredScopes` and `details.missingScopes` name what is missing. A key's scopes cannot be changed after it is issued, so create a new key with them. When `details.allowedActors` is present, no key can call this operation at all.
not_found	404	No resource of that id belongs to this account. A resource that belongs to somebody else answers 404 as well, never 403.	Check the id. Do not treat this as a permissions problem.
rate_limited	429	The credential's per minute budget, the account's per minute ceiling, or a daily cap was exceeded. `details.scope` is `minute`, `day` or `account`, or `global` when the product's own daily cap on voice previews is spent.	Wait the `Retry-After` seconds and retry. `details.limit` and `details.resetAt` say what was hit and when it reopens. The `RateLimit-*` headers on every answer let a client pace itself before it gets here.
internal_error	500	An unhandled failure inside this API. The original message is logged and never answered.	Retry once, then quote `requestId` to support. A 5xx deletes the idempotency claim rather than storing it, so retrying under the same key is safe.