New Features

Single token for many requests

Going forward, you can get one access token for your team and use it to perform many requests for many tenants. You can now use query parameter {tenant} to specify for which tenant you want to run the operation. The main advantages of this solution are:

  • Easier development of multi-tenant services.
  • Reduced number of calls to the OAuth service, and therefore reduced latency.
  • Reduced token cache size.

Get a list of all tenants for a client

To improve development and management of multi-tenant services, a new function to list of all tenants for a given client is introduced. You can now use simple GET method on the /all endpoint to retrieve this list.

Extended delete function to delete all service data for tenant, and a new hybris.media_admin scope

The delete functionality has been extended to enable you to delete all tenant data with just one call. This is a useful feature if you want to perform a cleanup after testing. You can trigger the deletion of all tenant data by using the DELETE method on the /{tenant}/{client}/ endpoint. To prevent the unintentional removal of service data, a new hybris.document_admin scope has been added.

  • Send feedback

    If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.

  • Get Help

    Use our private help channel. Receive updates over email and contact our specialists directly.

  • hybris Experts

    If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.