This is in terms of what is bad documentation and not architecture of the APIs per say (that is a whole other discussion!)
- Missing example implementation
- Missing error cases/scenarios. And no proper error redressal steps.
- Improper organisation of the APIs. There has to be a logical way of listing your APIs, so that its intuitive to look for a particular one.