stoney mail: Mail Resource - REST API

stoney mail

stoney mail: Mail Domains Resource - REST API
stoney mail: Mail Accounts Resource - REST API

https://api.example.com/v1/services/mail
https://api.example.com/v1/services/mail/domains
https://api.example.com/v1/services/mail/domains/5000000
https://api.example.com/v1/services/mail/domains/5000000/accounts
https://api.example.com/v1/services/mail/domains/5000000/accounts/5000001
https://api.example.com/v1/services/mail/domains/5000000/aliases/5000002
https://api.example.com/v1/services/mail/domainaliases
https://api.example.com/v1/services/mail/domainaliases/5000003
https://api.example.com/v1/services/mail/accounts
https://api.example.com/v1/services/mail/accounts/5000001
https://api.example.com/v1/services/mail/aliases
https://api.example.com/v1/services/mail/aliases/5000002

Notes

• Points we need to discuss --Chrigu (talk) 09:35, 30 January 2014 (CET)
  • services vs. products
    • Product: stone mail, stoney vm, stoney backup --Michael (talk) 09:47, 30 January 2014 (CET)
    • Service: mail domains and accounts, backup accounts, virtual machines (as defined in the directory under ou=services https://api.example.com/v1/services/vm/vms
  • product UIDs vs. names (mail/12345678 vs. mail/example.com)
    • Maybe both should work? If not, uid would be preferable, as they stay fix, even if you rename the mail account. --Michael (talk) 09:47, 30 January 2014 (CET)
  • Maybe create examples for other products/services to get a feeling about what is the better, more generic way.
    • See above. --Michael (talk) 09:47, 30 January 2014 (CET)