Actions220
- Additional Field (v2) Actions
- Address (v2) Actions
- Address Format (v2) Actions
- Attachment (v2) Actions
- Cache (v2) Actions
- Category (v2) Actions
- Category Icon (v2) Actions
- Category Image (v2) Actions
- Country (v2) Actions
- Cronjob (v2) Actions
- Currency (v3) Actions
- Customer (v3) Actions
- Customer Group (v2) Actions
- Customer (v2) Actions
- Email (v2) Actions
- Language (v2) Actions
- Manufacturer (v2) Actions
- Order (v2) Actions
- Order History (v2) Actions
- Order Item (v2) Actions
- Order Item Attribute (v2) Actions
- Order Status (v2) Actions
- Order Total (v2) Actions
- Order Tracking Code (v2) Actions
- Parcel Service (v2) Actions
- Payment Details (v2) Actions
- Product (v2) Actions
- Product Additional Field (v2) Actions
- Product Image (v2) Actions
- Product Link (v2) Actions
- Product Price (v2) Actions
- Quantity Unit (v2) Actions
- Review (v2) Actions
- Shop Information (v2) Actions
- Special Offer (v2) Actions
- Tax (v2) Actions
- Tracking Code (v2) Actions
- VPE (v2) Actions
- Withdrawal (v2) Actions
- Zone (v2) Actions
- Customer Addon Value (v3) Actions
- Customer Memo (v3) Actions
- Image List (v3) Actions
- Option (v3) Actions
- Parcel Service (v3) Actions
- Product Option (v3) Actions
- Product Variant (v3) Actions
- Tracking Code (v3) Actions
- Withdrawal (v3) Actions
Customer Memo (v3) → Update
AI-generatedSummary
Update a customer memo in the Gambio v3 API.
Inputs
- customerId (required) — ID of the customer.
- memoId (required) — ID of the memo to update.
- content (required) — New content for the memo.
Output shape
The updated customer memo resource is returned as the primary response payload.
No explicit post-receive routing is defined for the Update operation in the source; the API response body contains the memo data.
Examples
Example 1: Update memo content for customer 42, memo 7
Set customerId=42, memoId=7, content='New memo text'. Authentication defaults to basicAuth unless a bearer token is configured.