Do I need docs with request/response examples for every endpoint?

Not necessarily.

You usually want request/response examples for the most important or most complex endpoints, not every single one. A good rule of thumb:

Include examples when the endpoint:

• has non-obvious parameters
• returns complex or nested JSON
• has multiple possible responses or error cases
• is commonly used by integrators
• behaves differently depending on headers, query params, or auth

You can often skip examples when the endpoint:

• is very simple and self-explanatory
• follows the same pattern as other documented endpoints
• is internal-only or rarely used
• would just repeat the same structure over and over

Good documentation balance

For most APIs, a better setup is:

• one clear example per major endpoint
• one or two representative examples for each pattern
• shared schema/reference docs for common objects
• error response examples for important failures

If you’re using OpenAPI / Swagger

It’s especially useful to add examples for:

• request bodies
• successful responses
• error responses
• any field with tricky formatting

If you want, I can also give you a practical checklist for deciding which endpoints should get examples.