> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Portal Sessions

> Discover portal sessions and retrieve their check-in progress, submitted fields, orders, tickets, and stored assets.

Portal session reads are available to platform operators through REST and MCP.

| Operation          | REST                                                             | MCP                    | Permission       |
| ------------------ | ---------------------------------------------------------------- | ---------------------- | ---------------- |
| List sessions      | `GET /v1/workspaces/{workspace_id}/portal-sessions`              | `list_portal_sessions` | `View Upsells`   |
| Get session detail | `GET /v1/workspaces/{workspace_id}/portal-sessions/{session_id}` | `get_portal_session`   | `Manage Upsells` |

The list response includes session, contact, reservation, and submission identifiers plus progress counts. Use `submission_id` to determine whether a returned session has a check-in submission. The detail response includes all configured step types, submitted field values, safe order summaries, related tickets, and a flattened `assets` array.

<Note>
  Check-in progress is reservation-scoped. When multiple sessions belong to the
  same reservation, `submission.origin_session_id` identifies the session that
  originally collected the submission.
</Note>

## Uploaded files

Conduit-stored files are returned as download URLs rather than inline bytes. Assets identify their step, kind, subject, document type, and configured field. Provider-hosted ID images that Conduit does not store have a `null` download URL and `unavailable_reason: "provider_hosted"`.

The detail operation can expose government ID, selfie, signature, and guest information. Keep its output within systems authorized to handle that data.