Skip to main content

· 2 min read

The API MessageRegistry 3.0 is uploaded in the specification page. It is available for Document Providers in order to implement it. Document Senders and Document Consumers should wait that the Document Provider finished the implementation before using it.

The API Partition is uploaded in the specification page too.

The documentation page on the consultaton part of the Document Provider is modified for the use of the API 3.0 and the partition feature. The changes are:

· One min read

Our Oauth Team has asked for all services secured with Oauth to migrate to version 4 of the Oauth API. We have tested this using the oauth example.

The migration is pretty straightforward:

  • Change the oauth URL (the 3 becomes a 4)
  • Change the audience (BEWARE that the audience is totally different!)
  • That's all folks!

Go to this page to find the exact values

This needs to be done in both ACC and PRD. Test it with the UI as usual and if you which to make a side deployment of your service, don't forget that you can use the local dp feature


  • Can Oauth V3 clients use a service secured with Oauth v4: Yes, the ui will continue using v3 tokens until all Document Providers have migrated to v4.

· 2 min read

After a few months of good services it is time to retire our unofficial github technical support site. It has been a great platform for trying out new ways to document and provide support to the enterprise e-Box community, and it's success led to the creation of a new reference technical documentation site following the same principles:

  • Editable in Github: This was the great innovation for us, allowing us to push new and improved content in minutes
  • Accessible to all: Might be a surprise but this is something new for us :). Usually our documentation access is restricted.
  • Technically minded and straight to the point with heavy use of examples and code snippets

This new version of the site adds the following:

  • Double side bar navigation to easily navigate the content
  • Full merger of our legacy cookbook content into the new format
  • Hosted under an official domain
  • A Blog section for communications

To achieve this we used great tools like Docusaurus for the Documentation Site, Vercel for the hosting and Github for the version control.

This is pretty much a work in progress so don't hesitate to let us know is somethings can be improved!