• Remove tenant from URL

  • Replace /tenants/{tenant_name}/phonebooks/{id} for /phonebook/{uuid}

  • Must pass tenant inside headers

• Remove usage of ID in favor of UUID

  • Phonebook should be UUID

  • Contact have ID field but it’s an UUID (rename)

Questions

• How we deprecate a route

Requirements

• keep previous API fully functional

• add uuid identifier for phonebook

• add new phonebook API with phonebook uuid as identifier

• support multitenancy transparently through HTTP headers, token

  • support “hierarchical” tenant access(i.e. with ?recursive=true query parameter allowing to access resources from all subtenant tree)