ID of the client session.
IDs of the Connect Webviews associated with the client session.
IDs of the connected accounts associated with the client session.
Date and time at which the client session was created.
Optionalcustomer_Customer key associated with the client session.
Number of devices associated with the client session.
Date and time at which the client session expires.
Client session token associated with the client session.
Your user ID for the user associated with the client session.
Optionaluser_ID of the user identity associated with the client session.
IDs of the user identities associated with the client session.
ID of the workspace associated with the client session.
Represents a client session. If you want to restrict your users' access to their own devices, use client sessions.
You create each client session with a custom
user_identifier_key. Normally, theuser_identifier_keyis a user ID that your application provides.When calling the Seam API from your backend using an API key, you can pass the
user_identifier_keyas a parameter to limit results to the associated client session. For example,/devices/list?user_identifier_key=123only returns devices associated with the client session created with theuser_identifier_key123.A client session has a token that you can use with the Seam JavaScript SDK to make requests from the client (browser) directly to the Seam API. The token restricts the user's access to only the devices that they own.
See also Get Started with React.