Crash Report

[profispojka]

Error: Request failed with status 200:

Stack Trace:

Error: Request failed with status 200: 
    at s (file:///Users/jiricq/Desktop/personal%20projects/autosell/autosell/src/frontend/node_modules/.pnpm/@hey-api+openapi-ts@0.88.0_magicast@0.3.5_typescript@5.9.2/node_modules/@hey-api/openapi-ts/dist/src-C88NdVoQ.js:1:12602)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Promise.all (index 0)
    at async G (file:///Users/jiricq/Desktop/personal%20projects/autosell/autosell/src/frontend/node_modules/.pnpm/@hey-api+openapi-ts@0.88.0_magicast@0.3.5_typescript@5.9.2/node_modules/@hey-api/openapi-ts/dist/src-C88NdVoQ.js:1:12709)
    at async file:///Users/jiricq/Desktop/personal%20projects/autosell/autosell/src/frontend/node_modules/.pnpm/@hey-api+openapi-ts@0.88.0_magicast@0.3.5_typescript@5.9.2/node_modules/@hey-api/openapi-ts/dist/src-C88NdVoQ.js:10:2578
    at async Promise.all (index 0)
    at async te (file:///Users/jiricq/Desktop/personal%20projects/autosell/autosell/src/frontend/node_modules/.pnpm/@hey-api+openapi-ts@0.88.0_magicast@0.3.5_typescript@5.9.2/node_modules/@hey-api/openapi-ts/dist/src-C88NdVoQ.js:10:2525)
    at async file:///Users/jiricq/Desktop/personal%20projects/autosell/autosell/src/frontend/node_modules/.pnpm/@hey-api+openapi-ts@0.88.0_magicast@0.3.5_typescript@5.9.2/node_modules/@hey-api/openapi-ts/dist/run.js:2:1654

[dosubot]

Hi @profispojka! I'm Dosu and I’m helping the openapi-ts team.

This error usually means the API returned a status 200, but the response body didn't match the schema expected by the generated client. The @hey-api/openapi-ts clients validate response data against your OpenAPI spec, so if the response is missing fields, has the wrong types, or is otherwise malformed, you'll get an error even if the HTTP status is 200 (docs).

To debug, log the actual response body and compare it to the expected schema in your OpenAPI definition. You can use a response interceptor to inspect or modify the response before validation (interceptor docs). Also, check for recent changes in your API or schema that might have caused a mismatch.

If you need to isolate the issue, try sending a minimal request and see what the raw response looks like, or temporarily relax validation if possible. This should help pinpoint where the schema and response diverge.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

  

[mrlubos]

@profispojka this is a confusing one but you just need to make sure your server is running and serves the spec

[idealser]

I have same issue with .NET 10 serving OpenAPI 3.1. Absolutely same content provided through a file works with no issues. Once you provide the URL you get this:

[2025-11-23T18:53:16.090Z] Error: Request failed with status 200: 
Stack:
Error: Request failed with status 200: 
    at s (file:///C:/src/ui/node_modules/@hey-api/openapi-ts/dist/src-C88NdVoQ.js:1:12602)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Promise.all (index 0)
    at async G (file:///C:/src/ui/node_modules/@hey-api/openapi-ts/dist/src-C88NdVoQ.js:1:12709)
    at async file:///C:/src/ui/node_modules/@hey-api/openapi-ts/dist/src-C88NdVoQ.js:10:2578
    at async Promise.all (index 0)
    at async te (file:///C:/src/ui/node_modules/@hey-api/openapi-ts/dist/src-C88NdVoQ.js:10:2525)
    at async file:///C:/src/ui/node_modules/@hey-api/openapi-ts/dist/run.js:2:1654

config:

export default {
  input: 'https://localhost:5001/openapi/v1.json',
  output: 'src/app/shared/openapi',
  plugins: ['@hey-api/client-angular'],
};

curl:

StatusCode : 200
StatusDescription : OK
Content : {
                      "openapi": "3.1.1",
                      "info": {
                        "title": "API | v1",
                        "version": "1.0.0"
                      },
                      "servers": [
                        {
                          "url": "https://localhost:5001/"
                        }
                      ],
                      "paths": {
                        "/audit-lo...
RawContent : HTTP/1.1 200 OK
                    Transfer-Encoding: chunked
                    Content-Type: application/json;charset=utf-8
                    Date: Sun, 23 Nov 2025 18:50:45 GMT
                    Server: Kestrel
                    {
                      "openapi": "3.1.1",
                      "info": {
                        "title": "...
Forms : {}
Headers : {[Transfer-Encoding, chunked], [Content-Type, application/json;charset=utf-8], [Date, Sun, 23 Nov 2025 18:50:45 GMT], [Server, Kestrel]}
Images : {}
InputFields : {}
Links : {}
ParsedHtml : mshtml.HTMLDocumentClass
RawContentLength : 136116

[mrlubos]

@idealser are you able to confirm if the server ever gets hit? If so, with which method and how many times?

[idealser]

@mrlubos Sorry, forgot to mention it. It doesn't. No calls present.

UPD: Once I provide any public URL it starts hitting it (with/without port, with http/https). Could it be that localhost is not recognized?

[idealser]

Hosted the API on HTTP and it worked. Seems like it won't accept self-signed certificates:

#276 (comment)

If OP has same problems, I guess we can close this one.

[mrlubos]

@idealser ah yes that could be it. Considering this is mentioned on the Configuration and Input pages, I'm curious how we got here. Did you come across the package somewhere this isn't mentioned? I'm also not sure if we can surface a better error message for this issue, though that 200 is a known problem

[idealser]

My fault. I've discovered the package from some Reddit topic and I've got straight to the angular plugin. Was so impressed with the simplicity of the package and I was too impatient to not try it out right now that I didn't even expect it not working with this setup. Then found out this issue, and started to investigate. Eventually found the right place in the docs :)

The only thing that makes this issue unclear when you blindly configure it is that it tells you about 200 and you might get the wrong impression that the endpoint was actually called. Would never expect from such output that the route cause is the certificate.

[mrlubos]

@idealser gotcha, thanks for letting me know! I'll keep this open as a reminder to fix that 200 status bug