Deliver channel status
const url = 'https://shareout.site/v1/artifacts/example/deliver';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://shareout.site/v1/artifacts/example/deliver \ --header 'Authorization: Bearer <token>'Per-channel connection status for the Home Inspector Deliver section — whether Telegram is linked for the signed-in user, Slack is connected for the artifact workspace (with OAuth connectUrl when not), email is always available (with the caller’s own address), and the caller’s role.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Artifact ID (e.g. art_abc123).
Responses
Section titled “Responses”Channel status
object
object
object
object
The signed-in user’s own email — the default recipient.
Caller’s role on the artifact. Viewers may only schedule or deliver to themselves (own email, own Telegram, Slack DM).
Example
{ "role": "owner"}Access denied
object
Human-readable message.
Machine-readable error code.
Correlation id (also the X-Request-Id header). Quote it in support tickets.
Finer cause under code. For UNAUTHORIZED: missing, invalid, revoked or expired.
What to do next, in plain words.
The request field at fault.
Doc page for this error.
Present on 5xx — how to reach a human.
object
Example
{ "success": false, "support": { "how": "POST /v1/support/tickets", "include": [ "request_id" ] }}