Read one connection's metadata
Requires scope
connection:readReturns metadata only. The stored credential is tagged json:"-" in the model and is NEVER serialised — no endpoint anywhere lets you read back a secret you wrote.
Unlike the list projection, this response carries the real workspaceId, orgId and createdBy.
A connection in another workspace answers 404, not 403: existence is not disclosed across tenants.
Authorization
bearerAuth AuthorizationBearer <token>
An API token: Authorization: Bearer grt_…. Mint one in the app under Settings → Workspace → API tokens; the raw value is shown once. Scopes confine the token — see x-permission on each operation.
In: header
Path Parameters
id*string
The connection's UUID.
Format
uuidResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/connections/497f6eca-6276-4993-bfeb-53cbbbba6f08"{ "data": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "pieceId": "string", "name": "string", "authType": "string", "status": "active", "lastTestedAt": "2019-08-24T14:15:22Z", "tokenExpiresAt": "2019-08-24T14:15:22Z", "workspaceId": "ef0efa32-d1c1-43d4-a5e2-fe7b4f00403c", "orgId": "25b2c2d5-a7fc-47d0-89e4-8709a1560bfa", "createdBy": "25a02396-1048-48f9-bf93-102d2fb7895e", "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z" }}