Channels

For data that lives in an outside account: Gmail and Microsoft 365 mailboxes and calendars, LinkedIn, Google Drive and OneDrive / SharePoint, and the social surfaces. Connecting one is a consent step that happens in the provider's own browser flow; after it, a sync pulls the history in and synced content becomes ordinary corpus. Scanning, reading and managing a connected channel are catalog actions on the Actions lane (`channel_scan`, `channel_read`, `channel_manage`). What a channel sends lives in the Act leg's Outbound lane, where the approval gate is the story.

GET/v1/user/channelsSession

List connected channels

Read which channels are connected, their health, and when each last synced.

A channel that has fallen out of authorization reports it here rather than failing silently on the next sync — check this before concluding a sync returned nothing because there was nothing.

Request · curl

curl -X GET "https://runlogai.com/runlogapi/user/channels" \
  -H "Authorization: Bearer $RUNLOG_SESSION_TOKEN" \
  -H "X-Project-Id: p7Kd2mQx"

Response · 200

{
  "channels": [
    {
      "account": "amber@example.com",
      "channelId": "ch_6Wr4Bn",
      "kind": "email",
      "lastSyncedAt": "2026-08-07T18:31:44Z",
      "status": "connected"
    }
  ]
}

Errors

Status	error	When
401	unauthorized	No valid session.

POST/v1/channelsSession

Begin a connection

Start a channel connection and receive the consent link to send the account holder to.

Connection cannot be completed by API, by design: the account holder authorizes it in their own provider's browser flow. This route returns the link; the connection lands when they finish it.

A connection needing a second factor pauses at a checkpoint, which the same lane resolves once the holder supplies it.

Body

Field	Type	Required	Description
action	string	required	`connect-link` for the hosted flow, `reconnect-link` to re-authorize an existing channel.
kind	string	required	The channel kind to connect: `email`, `calendar`, `professional-network`, `store`, `social`.
provider	string	optional	Which account within the kind: `gmail`, `microsoft-365`, `linkedin`, `google-drive`, `onedrive`, `meta`, `tiktok`. Defaults to the only provider serving that kind.

Request · curl

curl -X POST "https://runlogai.com/runlogapi/channels" \
  -H "Authorization: Bearer $RUNLOG_SESSION_TOKEN" \
  -H "X-Project-Id: p7Kd2mQx" \
  -H "Content-Type: application/json" \
  -d '{
  "action": "connect-link",
  "kind": "email",
  "provider": "gmail"
}'

Response · 200

{
  "expiresAt": "2026-08-07T19:00:00Z",
  "url": "https://connect.runlogai.com/…"
}

Errors

Status	error	When
400	invalid request body	The body is not JSON, or exceeds the 1 MB request-body cap.
401	invalid API key	The `Authorization` header is missing, malformed, or names a revoked key.
400	name the target project via the X-Project-Id header or projectId query	No project was named and the key is not bound to one.
429	rate limit exceeded	You passed 60 requests/minute on this key. `Retry-After` carries the seconds to wait.
500	internal error	The relay failed to serve the request. Retry with backoff; the cause is logged server-side against your request.

POST/v1/channel-sync/{channelId}API key

Sync a channel

Pull the channel's history into the project's corpus, where retrieval reaches it.

Incremental after the first run: a sync resumes from its own watermark, so calling it repeatedly is cheap and calling it twice is not a duplicate.

Synced content becomes ordinary corpus. A question about what a customer said in an email is answered by the same retrieval that answers a question about a file.

Path parameters

Field	Type	Required	Description
channelId	string	required	The connected channel to sync.

Request · curl

curl -X POST "https://runlogai.com/runlogapi/channel-sync/ch_6Wr4Bn" \
  -H "Authorization: Bearer $RUNLOG_API_KEY" \
  -H "X-Project-Id: p7Kd2mQx" \
  -H "Content-Type: application/json" \
  -d '{}'

Response · 202

{
  "status": "started"
}

Errors

Status	error	When
400	channel does not support sync	The channel's kind has no history to pull.
404	unknown channel	This project holds no such channel.
409	running	A sync of this channel is already running; the body is `{status: "running"}`.
401	invalid API key	The `Authorization` header is missing, malformed, or names a revoked key.
400	name the target project via the X-Project-Id header or projectId query	No project was named and the key is not bound to one.
429	rate limit exceeded	You passed 60 requests/minute on this key. `Retry-After` carries the seconds to wait.
500	internal error	The relay failed to serve the request. Retry with backoff; the cause is logged server-side against your request.