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.
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.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 anull 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.