Thank you so much for your comment!

Regarding the question you made, in your case, I don't see any added value in introducing HATEOAS, because you say you have a well-documented API and it's only for internal use.

I have had experiences, in a similar situation, where documentation was poor, and having HATEOAS would've helped a lot in getting to know the API not only as fast as possible but in a deeper way.

If you had your API publically available, I would recommend HATEOAS because I think it would make the other developers' lives easier, but this comes with the cost of having a bit of extra work to give this "client" experience.