Skip to content

Whether a new key has been called yet (the connect dialog's last step)

GET
/api/v1/workspaces/{workspace}/integrations/connections/{id}/status
curl --request GET \
--url https://reputecast.example.com/api/v1/workspaces/acme-newsletter/integrations/connections/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/status \
--header 'Authorization: Bearer <token>'

Permission: integrations:view

workspace
required

Workspace slug

string
/^[a-z0-9][a-z0-9-]{1,62}$/

Workspace slug

id
required
string format: uuid

OK

Media typeapplication/json
object
firstCall
object
at
required
string format: date-time
client
string
ip
string
operation
required
string
status
required
integer format: int32
keyCreatedAt
string format: date-time
reported
string format: date-time
status
required
string
Allowed values: waiting connected attention

Example

{
"status": "waiting"
}

Error

Media typeapplication/problem+json
object
code

Stable error code, e.g. permission_denied

string
detail

A human-readable explanation specific to this occurrence of the problem.

string
errors

Optional list of individual error details

Array<object>
object
location

Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’

string
message

Error message text

string
value

The value at the given location

helpers

Members who hold the missing permission

Array<string>
instance

A URI reference that identifies the specific occurrence of the problem.

string format: uri
meta
object
key
additional properties
permission

The missing permission key

string
status

HTTP status code

integer format: int64
title

A short, human-readable summary of the problem type. This value should not change between occurrences of the error.

string
type

A URI reference to human-readable documentation for the error.

string format: uri
default: about:blank

Example

{
"detail": "Property foo is required but is missing.",
"instance": "https://example.com/error-log/abc123",
"status": 400,
"title": "Bad Request",
"type": "about:blank"
}