Problem with using rest API after moving to v016

Questions
1

Your question

previous version of stalwart, if i curl to http:/x/:8080/api/principal it would response “you have to auth first”. And I can programatically use a Bearer token and all fine.
v016 answers “the requested resource does not exist on this server”.
curl http:/x/:8080/admin/login renders ok, so server is running on that port etc. where should I start to search for config errors?

I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.

on

2

What’s changing

The existing REST API for configuration and management is being replaced by a JMAP-based API. Every setting is represented as a JMAP object, and every management action is performed through JMAP method calls.

3

Thanks. Explains it. However create a lot of work. I also liked the account name<> email address solution before.

4

The old REST /api/* management endpoints were removed in 0.16; management is now done through JMAP method calls (authenticated with a Bearer token as before, against the JMAP session URL), so the 404 is expected. @root_root had this right above.

For scripting, the supported path is stalwart-cli, which drives the same JMAP API. See stalw.art/docs/migration for the change.