Doc Feedback:Clarify default error response format across API Manager versions

Open Beginner friendly

#10,660 opened on Feb 4, 2026 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 1/5
Estimated time: Under an hour
Newbie friendliness: 72/100

Issue type: Documentation
Clarity: Clearly specified
Activity status: Quiet
Domain: api, documentation

Research direction

Start with the error-handling page at https://apim.docs.wso2.com/en/4.0.0/troubleshooting/error-handling/ and compare its wording with the 4.6.0 documentation. Add a short note explaining that the default error response format depends on the API Manager version, then verify that the distinction between XML in older versions and JSON in newer versions is clear.

Written by the indexing model from the issue text.

Description

Location : https://apim.docs.wso2.com/en/4.0.0/troubleshooting/error-handling/

Description:
The documentation states that the API Manager throws XML based error responses by default in version 4.0.0.
However in newer versions ( 4.6.0) the documentation states that JSON based error responses are returned by default.

While this behavior is correct per version, it can be confusing when comparing documentation across versions without an explicit clarification.

Add a short note indicating that the default error response format is version dependent
(XML in older versions and JSON in newer versions) to improve clarity.

Dominant language: CSS
Stars: 99
Forks: 708
Avg merge: 1d 7h
Merged PRs (30d): 22

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug]: Matrix progress drafts fail with "Matrix runtime not initialized" during tool activity Open

bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

openclaw/openclaw#155298 · 2 comments · 1 reaction · Opened Sep 22, 2026
[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
MCP client has no httpx timeout, so the event stream fails after 5 seconds Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

Azure/azure-functions-agents-runtime#228 · Opened Sep 21, 2026
feat(mcp): friendlier error when `run_cloud_sync` is called on a disabled connection Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

airbytehq/PyAirbyte#1205 · Opened Sep 21, 2026

More Backend & API Design issues