The other day I asked for an analysis or at least an UML diagram since we are having quite some troubles and my boss looked disgusted at me for asking such a question. I’m not a professional backend developer, so I don’t know how it works professionally
I think you misunderstood, I’m the one implementing the API and writing the queries - alongside a coworker that doesn’t have BE experience. I’m not the one who made the DB though, neither is he, and the design is not very reliable
You said you were in the role of the “front end dev”. I presumed a structure of an API (usually implemented by a “backend dev”), and a UI (usually implemented by a “front end dev”).
My advice still stands:
You need to clarify the interface where each of your responsibilities are handed off.
If you are implementing the API, you can still produce the same document and then you need to get the other people that need to use it to verify that they can build what they’re doing from that. This means they will need to map the data from the API into the UI elements they need to provide. It also means that someone will need to see how that data will be sourced from the database, and identify anything that is not available in the database.