Memos unofficial
PATCH/api/v1/memos/{memo}/attachments

Replace a memo's attachments

Replaces the full set of attachments associated with a memo. Pass the complete desired list in attachments; an empty list clears the memo's attachments, and repeating the same request is idempotent.

  • IdempotentThe SDK sends Idempotency-Key, so a retried request is only applied once.

1 parameter · 2 body fields
memostringrequired
The identifier of the memo whose attachments to replace.

The memo resource name and the complete attachment list to set.

namestringrequired
Required. The resource name of the memo. Format: memos/{memo}
attachmentsarray<object>required
Required. The attachments to set for the memo.

2 status codes
200Returns an empty response after replacing the memo's attachment list.
defaultDefault error response
codeintegeroptional
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
messagestringoptional
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
detailsarray<object>optional
A list of messages that carry the error details. There is a common set of message types for APIs to use.

Error handling

The memo path parameter must identify the memo to update. The body must include name and attachments, and each attachment must include filename and type; pass the full desired attachment set because this operation replaces rather than appends.