[Feature Request] - Response from the createRoutingRule endpoint.

[alicethefemme]

Suggested in a Helpdesk ticket, the current route https://purelymail.com/api/v0/createRoutingRule doesn't currently have the response send back the ID for the routing rule, which assists in the process of deletion later.

Testing with demo account and postman, the following is the provided response when creating a routing rule:

Allowing for the ID to return will help improve certain workflows which allows users to create "one time use" or "10 minute mail" like email addresses using the routing rules.

[vic1707]

Duplicate of https://github.com/Purelymail/purelymail-issues/issues/343 (which I'll close),

Probably worth noting that many endpoints do that:

• Creation endpoints /api/v0/createUser, /api/v0/addDomain, api/v0/createRoutingRule
• Edition endpoints: /api/v0/modifyUser, /api/v0/upsertPasswordReset, /api/v0/updateDomainSettings
• Deletion endpoints /api/v0/deleteUser, /api/v0/deletePasswordReset, /api/v0/deleteRoutingRule, /api/v0/deleteDomain, /api/v0/deleteAppPassword

It would be really helpful if all Creation and Edition endpoint could return the current state. For deletion endpoints I haven't used them all at the moment (only used /api/v0/deleteRoutingRule & /api/v0/deleteDomain which are find with empty responses)

[vic1707]

Also worth noting that /api/v0/listUser returns a list of usernames not the complete user object settings (getUser does that but one user at a time) would be helpful to get the full output