Create read — POST /v1/team/inbox/{id}/read

Marks one of the caller's notifications read and answers it.

POST /v1/team/inbox/{id}/read

Addresshttps://api.hanzo.ai/v1/team/inbox/{id}/read
MethodPOST
Operationpost_team_inbox_by_id_read
AuthAuthorization: Bearer $HANZO_API_KEY

Marks one of the caller's notifications read and answers it. Another person's notification is a 404, as one that does not exist is.

Request

3 fields, body application/json (required).

FieldInTypeRequiredDescription
idpathstringyesID is the notification, from the path.
idbodystring—ID is the notification, from the path.
spacebodystring—Space is the space uuid it was filed in.

Response

StatusBodyMeaning
200team.teamInboxItemok
defaultproblem-detailsrefused

200 body — 31 fields.

FieldInTypeAlwaysDescription
archivedbodyboolean—Archived reports that the caller archived it.
channelbodystring—Channel is the channel it is about, when it is about a channel.
createdOnbodyinteger (int64)—CreatedOn is when it was filed, unix milliseconds.
docbodystring—Doc is the document it is about, when it is about a document.
idbodystring—ID is the notification's own id — what read and archive address.
messagebodyteam.teamMessage—
message.authorbodystring—Author is the team account uuid that wrote it.
message.channelbodystring—Channel is the channel it was said in — the same id the channel listing answers with, so a caller holding a message can name its channel without a second read.
message.createdOnbodyinteger (int64)—CreatedOn is unix MILLIseconds, which is what the platform stamps.
message.docbodystring—Doc is the document this message is a comment on.
message.editedOnbodyinteger (int64)—EditedOn is when the author last edited the message, unix milliseconds.
message.filesbodyteam.teamFile[]—Files are the files attached to the message.
message.files[].filebodystring—File is the blob id, readable at GET /v1/team/files/{space}/{name}?file={file}.
message.files[].idbodystring—ID is the attachment document's own id.
message.files[].namebodystring—Name is the file's name as the person uploaded it.
message.files[].sizebodyinteger (int64)—Size is the file's length in bytes, as the uploader stated it.
message.files[].typebodystring—Type is the media type the uploader declared.
message.idbodystring—ID is the message document's own id.
message.lastReplybodyinteger (int64)—LastReply is when the thread was last answered, unix milliseconds.
message.mentionsbodystring[]—Mentions are the account uuids the message @-mentions — exactly the people notify.go told they were mentioned.
message.reactionsbodyteam.teamReaction[]—Reactions are the emoji people reacted with, one entry per emoji, in the order each emoji was first used.
message.reactions[].accountsbodystring[]—Accounts are the account uuids that reacted with it, earliest first.
message.reactions[].countbodyinteger (int64)—Count is how many people reacted with it.
message.reactions[].emojibodystring—Emoji is the reaction itself, as the person picked it.
message.repliesbodyinteger (int64)—Replies is how many replies the message's thread holds.
message.textbodystring—Text is the message as PLAIN TEXT.
message.threadbodystring—Thread is the message this one replies to.
readbodyboolean—Read reports that the caller has seen it.
reasonbodystring—Reason is why it was filed: "mention", "dm" (a direct message), "reply" (in a thread the caller is in), "comment" (on something the caller follows), "assigned", or "other".
spacebodystring—Space is the space uuid it was filed in.
threadbodystring—Thread is the message whose thread it is about, for a reply.

Failure carries the platform error shape — see Errors.

Examples

hanzo team inbox read <id>
import { Configuration, TeamApi } from 'hanzoai';

const api = new TeamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postTeamInboxByIdRead({ id: 'id', id: "<id>", space: "<space>" });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import TeamApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TeamApi(client).post_team_inbox_by_id_read(id='id', id="<id>", space="<space>")
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.TeamAPI.PostTeamInboxByIdRead(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, team_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = team_api::post_team_inbox_by_id_read(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.TeamApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new TeamApi(client).postTeamInboxByIdRead();
curl -X POST https://api.hanzo.ai/v1/team/inbox/<id>/read \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "id": "<id>",
       "space": "<space>"
     }'

MCP reaches team through the team tool, which names its 33 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_team_account_providers"
         }
       }
     }'

Team API · All Hanzo APIs · Interactive reference

Was this page useful?
Broken link or missing step? Drop it in #docs on Discord or open a PR.