Required. The space read state and fields to update. Only supports updating read state for the calling user. To refer to the calling user, set one of the following: - The me alias. For example, users/me/spaces/{space}/spaceReadState. - Their Workspace email address. For example, users/user@example.com/spaces/{space}/spaceReadState. - Their user id. For example, users/123456789/spaces/{space}/spaceReadState. Format: users/{user}/spaces/{space}/spaceReadState
Required. The field paths to update. Currently supported field paths: - last_read_time When the last_read_time is before the latest message create time, the space appears as unread in the UI. To mark the space as read, set last_read_time to any value later (larger) than the latest message create time. The last_read_time is coerced to match the latest message create time. Note that the space read state only affects the read state of messages that are visible in the space's top-level conversation. Replies in threads are unaffected by this timestamp, and instead rely on the thread read state.
getSpaceReadState
Required. The space read state and fields to update.
Only supports updating read state for the calling user.
To refer to the calling user, set one of the following:
The me alias. For example, users/me/spaces/{space}/spaceReadState.
Their Workspace email address. For example,
users/user@example.com/spaces/{space}/spaceReadState.
Their user id. For example,
users/123456789/spaces/{space}/spaceReadState.
Format: users/{user}/spaces/{space}/spaceReadState
Required. The field paths to update. Currently supported field paths:
last_read_time
When the last_read_time is before the latest message create time, the
space appears as unread in the UI.
To mark the space as read, set last_read_time to any value later (larger)
than the latest message create time. The last_read_time is coerced to
match the latest message create time. Note that the space read state only
affects the read state of messages that are visible in the space's
top-level conversation. Replies in threads are unaffected by this
timestamp, and instead rely on the thread read state.
Required. The field paths to update. Currently supported field paths:
last_read_time
When the last_read_time is before the latest message create time, the
space appears as unread in the UI.
To mark the space as read, set last_read_time to any value later (larger)
than the latest message create time. The last_read_time is coerced to
match the latest message create time. Note that the space read state only
affects the read state of messages that are visible in the space's
top-level conversation. Replies in threads are unaffected by this
timestamp, and instead rely on the thread read state.
Required. The field paths to update. Currently supported field paths:
last_read_time
When the last_read_time is before the latest message create time, the
space appears as unread in the UI.
To mark the space as read, set last_read_time to any value later (larger)
than the latest message create time. The last_read_time is coerced to
match the latest message create time. Note that the space read state only
affects the read state of messages that are visible in the space's
top-level conversation. Replies in threads are unaffected by this
timestamp, and instead rely on the thread read state.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Google Apps Chat V1 Client - Class UpdateSpaceReadStateRequest (0.12.0)\n\nVersion latestkeyboard_arrow_down\n\n- [0.12.0 (latest)](/php/docs/reference/apps-chat/latest/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.11.2](/php/docs/reference/apps-chat/0.11.2/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.10.0](/php/docs/reference/apps-chat/0.10.0/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.9.0](/php/docs/reference/apps-chat/0.9.0/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.8.1](/php/docs/reference/apps-chat/0.8.1/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.7.2](/php/docs/reference/apps-chat/0.7.2/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.6.1](/php/docs/reference/apps-chat/0.6.1/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.5.0](/php/docs/reference/apps-chat/0.5.0/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.4.0](/php/docs/reference/apps-chat/0.4.0/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.3.0](/php/docs/reference/apps-chat/0.3.0/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.2.0](/php/docs/reference/apps-chat/0.2.0/Chat.V1.UpdateSpaceReadStateRequest)\n- [0.1.4](/php/docs/reference/apps-chat/0.1.4/Chat.V1.UpdateSpaceReadStateRequest) \nReference documentation and code samples for the Google Apps Chat V1 Client class UpdateSpaceReadStateRequest.\n\nRequest message for UpdateSpaceReadState API.\n\nGenerated from protobuf message `google.chat.v1.UpdateSpaceReadStateRequest`\n\nNamespace\n---------\n\nGoogle \\\\ Apps \\\\ Chat \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getSpaceReadState\n\nRequired. The space read state and fields to update.\n\nOnly supports updating read state for the calling user.\nTo refer to the calling user, set one of the following:\n\n- The `me` alias. For example, `users/me/spaces/{space}/spaceReadState`.\n- Their Workspace email address. For example, `users/user@example.com/spaces/{space}/spaceReadState`.\n- Their user id. For example, `users/123456789/spaces/{space}/spaceReadState`. Format: users/{user}/spaces/{space}/spaceReadState\n\n### hasSpaceReadState\n\n### clearSpaceReadState\n\n### setSpaceReadState\n\nRequired. The space read state and fields to update.\n\nOnly supports updating read state for the calling user.\nTo refer to the calling user, set one of the following:\n\n- The `me` alias. For example, `users/me/spaces/{space}/spaceReadState`.\n- Their Workspace email address. For example, `users/user@example.com/spaces/{space}/spaceReadState`.\n- Their user id. For example, `users/123456789/spaces/{space}/spaceReadState`. Format: users/{user}/spaces/{space}/spaceReadState\n\n### getUpdateMask\n\nRequired. The field paths to update. Currently supported field paths:\n\n- `last_read_time` When the `last_read_time` is before the latest message create time, the space appears as unread in the UI.\n\nTo mark the space as read, set `last_read_time` to any value later (larger)\nthan the latest message create time. The `last_read_time` is coerced to\nmatch the latest message create time. Note that the space read state only\naffects the read state of messages that are visible in the space's\ntop-level conversation. Replies in threads are unaffected by this\ntimestamp, and instead rely on the thread read state.\n\n### hasUpdateMask\n\n### clearUpdateMask\n\n### setUpdateMask\n\nRequired. The field paths to update. Currently supported field paths:\n\n- `last_read_time` When the `last_read_time` is before the latest message create time, the space appears as unread in the UI.\n\nTo mark the space as read, set `last_read_time` to any value later (larger)\nthan the latest message create time. The `last_read_time` is coerced to\nmatch the latest message create time. Note that the space read state only\naffects the read state of messages that are visible in the space's\ntop-level conversation. Replies in threads are unaffected by this\ntimestamp, and instead rely on the thread read state.\n\n### static::build"]]