nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

API unification

jonnyg

Pardon me if this has been raised elsewhere – but it would be of great help if the 2 API's are unified.
We are customizing/extending the OOTB client code… which uses the so-call "internal" Rest API ("/app/rest/…") but we're going to need to change these all to use "api/enterprise/…" Won't be easy to maintain in the long run.

Find more posts tagged with

Comments

jbarrez

The idea behind the two is:

- /rest is 'internal', ie what the UI uses. It used cookie auth.
- /api is the public api (ie we can't change this overnight). I'd say 80% of the features is the same, but there are a few UI-specific calls in /rest. It uses basic auth though.

So when writing 'external' applications, the /api is the way to go. This is the 'public', 'stable' API.

jonnyg

Thanks. It would have been helpful if it were easier to go between the 2… i.e., if the public api is /api/enterprise, then the public API would be /x/api/enterprise.
We are extending/enhancing the OOTB application for our own use (converting it to a ui_grid + modal ux), and the less we need to change, the easier it will be to share back with you.