POST /api/msg/feed/save
This is NOT an append to the record: it writes to the user's vault, and a vault write can never alter the chain. Kept in this router because it is the feed's "save" action from the user's point of view.
| Method | POST |
| Path | /api/msg/feed/save |
| Domain | Messaging & files · Msg Feed |
| Tier | computation (public) |
| Auth | user |
Request
curl -X POST https://zeqsdk.com/api/msg/feed/save \
-H "Authorization: Bearer $ZEQ_KEY" \
-H "Content-Type: application/json" \
-d '{ }' # request body — see description
Needs a machine key — mint one free:
curl -X POST https://zeqsdk.com/api/demo-key/mint, then spin up your machine.
Generated from the node's own route registry (GET /api/endpoints) — this path is live.