feat(api_server.py): update error response handling for accurate OpenAPI schema

[RepoBirdBot]

This PR updates the error response definitions for several API endpoints in order to align the OpenAPI documentation with the actual behavior observed during testing. Previously, endpoints such as /tokenize, /detokenize, /v1/chat/completions, /v1/completions, /v1/audio/transcriptions, and /invocations had hardcoded responses definitions for HTTP 400 and 500 error responses. However, testing indicated that these error responses were not fully representative of the responses clients receive.

The changes in this PR remove the explicit responses parameters from the router decorators. This allows the API to rely on centralized error handling and default schema generation, ensuring that the OpenAPI spec dynamically reflects the error responses generated by the server, including the previously undocumented 400 and 500 status codes.

Closes #17037.

---

Created with Repobird.ai 📦🐦

[ariel-frischer]

👋 Hello from RepoBird.ai!

I'm the founder of RepoBird.ai, an AI Software Engineer Agent that integrates seamlessly as a GitHub App.

This Pull Request was automatically generated by our agent, RepoBirdBot, to address issue #17037. This issue was marked as a good first issue and appeared to be unassigned.

Why this PR?

• We're currently testing RepoBird by offering automated fixes for open-source projects like yours.
• Our goal is to help maintainers and provide useful contributions.
• We greatly value feedback from maintainers and early users during this phase.

Your Feedback Matters:

Please review the proposed changes. If this type of automated contribution isn't suitable for your repository, or if this specific PR isn't helpful, just let me know! I'll close it, make any improvements and unlist these PRs – no worries.

Want changes? If you have feedback or requested modifications, please leave comments directly on this PR. Once all review comments are in, comment @RepoBirdBot Update and I will manually run the agent again, taking into account all PR comments and any pipeline failure logs.

---

Interested in learning more?

• Visit Repobird.ai to explore our Agentic AI-driven code automation.
• Install the RepoBird GitHub App.

Thank you!

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[DarkLight1337]

@tarukumar can you help review this?

[tarukumar]

@DarkLight1337 Sure will review and try to test this fix as well

[davidxia]

@DarkLight1337 @tarukumar looks like this PR was made by a bot. I created a more comprehensive one here that also satisfies the DCO and handles a few more things. #17664

[davidxia]

@ariel-frischer hi, thanks for demoing RepoBird.ai.

appeared to be unassigned

If this is the expected behavior, there might be a bug in RepoBird.ai. I was assigned to #17037 about two weeks ago, but RepoBird.ai created this PR yesterday.

[ariel-frischer]

@ariel-frischer hi, thanks for demoing RepoBird.ai.

appeared to be unassigned

If this is the expected behavior, there might be a bug in RepoBird.ai. I was assigned to #17037 about two weeks ago, but RepoBird.ai created this PR yesterday.

Yes, kind of a bug possible we did scrape 2 weeks ago but did not sync to make it up to date - will have that fixed.

@DarkLight1337 @tarukumar looks like this PR was made by a bot. I created a more comprehensive one here that also satisfies the DCO and handles a few more things. #17664

Awesome will close this out then no worries.