Read the author's open Pixel conversation
const url = 'https://api.pixonaut.app/v1/pixel/conversation';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.pixonaut.app/v1/pixel/conversation \ --header 'Authorization: Bearer <token>'Operation ID: pixelConversation.get
A studio member’s open conversation, or the one a member holds in a connected store: a member key reads the conversation its member’s turns in that store hold, never the member’s studio one or another store’s.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The open conversation, or null when the author has none
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
Whether a turn, or a card being applied, holds the conversation now: one still running after the panel that asked for it closed. Read again until it is false to see what it did.
Examples
Example
{ "conversation": { "cards": {}, "contentKeys": {}, "id": "pcv_5f0c2a9e1b7d4c3a8e6f0b12", "messages": [ { "content": "Make a product for the Summer mug template", "role": "user" }, { "content": [ { "text": "Done: the Summer mug is on sale in the store.", "type": "text" } ], "role": "assistant" } ], "unavailable": [], "unseen": [], "uploads": {}, "upscaled": {} }, "working": false}Headers
Section titled “Headers”Every response names the request it answers in X-Request-Id: the id the request was sent with in that header, when it is well formed, else one the API gave it. Quote it when reporting a refusal or a failure: the API’s log lines for that request carry it.
Refused: unauthorized, member_link_required, member_link_revoked
object
Examples
member_link_required
{ "error": "member_link_required"}member_link_revoked
{ "error": "member_link_revoked"}unauthorized
{ "error": "unauthorized"}Headers
Section titled “Headers”Every response names the request it answers in X-Request-Id: the id the request was sent with in that header, when it is well formed, else one the API gave it. Quote it when reporting a refusal or a failure: the API’s log lines for that request carry it.
Refused: origin_forbidden, feature_disabled, forbidden, workspace_suspended
object
The feature the tenant does not have. Always sent with feature_disabled.
Examples
feature_disabled
{ "error": "feature_disabled", "feature": "api"}forbidden
{ "error": "forbidden"}origin_forbidden
{ "error": "origin_forbidden"}workspace_suspended
{ "error": "workspace_suspended"}Headers
Section titled “Headers”Every response names the request it answers in X-Request-Id: the id the request was sent with in that header, when it is well formed, else one the API gave it. Quote it when reporting a refusal or a failure: the API’s log lines for that request carry it.
Refused: db_error. A request that failed unexpectedly answers as text instead.
object
Examples
db_error
{ "error": "db_error"}Headers
Section titled “Headers”Every response names the request it answers in X-Request-Id: the id the request was sent with in that header, when it is well formed, else one the API gave it. Quote it when reporting a refusal or a failure: the API’s log lines for that request carry it.
Questions? Write to [email protected].