Choose the right tool up front because a single Rich Menu cannot be edited across OA Manager and the Messaging API.
The most important limitation
LINE states that one Rich Menu instance belongs to one management tool. A menu created in LINE Official Account Manager cannot be retrieved or edited with the Messaging API, and an API-created menu cannot be edited in OA Manager.
Decision table
Choose based on the operational requirements, not only on which interface feels familiar.
| Requirement | OA Manager | Messaging API |
|---|---|---|
| Fast, no-code setup | Best fit | Channel setup required |
| Free placement or automation | UI-dependent | Best fit |
| Postback, datetime, tab switching | Limited | Supported |
| Per-user menu | Not available | Supported |
| Display schedule | Built into the manager | Build the scheduling logic |
| Retrieve JSON and image | Use OA Manager | Use the API |
How to migrate when you chose the wrong tool
There is no direct command to migrate the same menu between tools. Keep the original artwork, recreate the areas and actions in the target tool, validate them, and publish a new Rich Menu.
Do not delete the old menu before testing the replacement on a phone. Set the new one as default only after validation, and retain the previous ID for a short rollback window.
Display priority when multiple menus exist
LINE prioritizes a per-user API menu, then the API default, then the OA Manager default. This explains why some users may still see a different menu after a default is changed.
Official references
Confirm the latest official specification before using a workflow in a critical system.
Ready to map it on a canvas?
Drag, move, and resize action areas, then validate the JSON before publishing.
Open Studio →