The MovingManifest API lets trusted tools create moves, add inventory, upload evidence, prepare sale listings, plan loads, and export documentation. Public docs are readable before login; private data requires a user-created API key.
API flow
Assistant-safe order
Create or update a move, origin/destination context, spaces, transport resources, transport zones, and starter inventory.
Create one item or batch upsert up to 100 items with dimensions, weight estimates, provenance, review flags, and disposition.
Upload JPEG, PNG, or WebP evidence in one API call as raw bytes, multipart form data, URL, data URL, or base64. Images get web-ready derivatives server-side, uploads can queue AI review suggestions, and direct uploads return agentReview summaries for quick user correction.
Prepare sale listings for sell-marked items with platform status, title, description, pricing, research depth, and buyer counts.
Fetch agent context, planned items, floor plans, resources, zones, capacity reports, and move-day checklists.
Use revocable API keys with explicit scopes. Add or invite household collaborators by email with the members/manage scope.
Assistants should avoid clicking around when the API can return a structured move context. Use dry runs for bulk changes, preserve provenance for estimates, and prefer batch endpoints over chatty loops.
https://movingmanifest.com/api/v1Authorization: Bearer mmk_...GET /me, GET /moves, GET /moves/{moveId}/agent-contextPOST /moves/{moveId}/items/batch-upsertPOST /images/upload or POST /photos/uploadGET /openapi.jsonThe Settings screen defaults to a useful assistant key. Users can still remove scopes, restrict a key to one move, rotate it, or revoke it after the helper session. Member management is an explicit extra scope because it grants real account access. A spouse or collaborator can be invited by email before they create an account; access activates when they sign in with that email.