Skip to main content
POST
Retrieve supporting metadata such as domains, folders, pixels, and organization information. The response shape depends on the resource you request. Each successful response is wrapped in the standard envelope (success, status_code, data, message). The data property matches the structure described in the table above.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
resource
enum<string>
required

Resource to fetch.

Available options:
domain,
folder,
tag,
pixel,
organization
workspace_id
integer

Workspace scope used for folder and tag lookups.

Response

Resource payload

success
boolean
required
Example:

true

status_code
integer
required
Example:

200

data
object
required
message
string
Example:

""