Endpoints present in my project show as 404 (Page not found) on documentation site

piovra · October 28, 2025, 10:52am

I have 2 endpoints that I have been working on today in my Endpoints section - they all show fine while I am editing them through either the web or desktop client.

However when I try to access them through the docs website, I get this error:

404
Page not found

These are the ids for the 2 endpoints:

https://app.apidog.com/link/project/1073463/apis/api-23425003
https://app.apidog.com/link/project/1073463/apis/api-23423915

Also note that when I do the Generate Server Stubs and Client SDKs from the top of the folder that creates these endpoints, these 2 endpoints do not have code generated for them.

The rest of the endpoints on the website get displayed fine and have the code generation also working ok for them.

Can you please let me know as soon as you have a chance what is going on? These are important endpoints and our users cannot access them.

Apidog Support · October 28, 2025, 11:19am

Hi Sandu, could you please share your documentation URL? Also, could you confirm if these two problematic endpoints are set as “shared”? (If they’re marked as “internal”, they won’t be accessible in the documentation.)

piovra · October 28, 2025, 11:39am

They are both set as Shared. According the value in the URL Slug they should show up at:

Just to add: they do show up in the menus on the docs, but I get the 404 when I click on the leaf nodes.

piovra · October 28, 2025, 11:43am

you can DM me for the password

Apidog Support · October 28, 2025, 12:03pm

Okay, Emily will DM you to follow up on this issue.

Apidog Support · October 28, 2025, 12:55pm

The issue has been fixed. Please refresh the page and try again:

piovra · October 28, 2025, 1:01pm

beautiful! thank you much for the prompt response! both the docs and code generation work now.

Have I done something wrong (to avoid in the future) on my side to trip up the system?

Apidog Support · October 28, 2025, 2:53pm

We’ve identified and resolved the special data case in our system, so everything should be working normally for you now. We’ll optimize our system logic to better handle similar scenarios in the future. Let us know if you encounter any other issues.

piovra · October 28, 2025, 5:56pm

Hi I am encoutering again half of the issues, I’ve noticed earlier:

i.e. the code generation acts just like before:

the createAccount operationId on this request:
Vulcan Forge

Does not get generated any longer out in the output.

The createFinancialInstrument operationId from this:
Vulcan Forge

Is generated like this:

apiV1FinancialInstrumentsPost: async (solanaClusterId?: string, xRequestId?: string, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
            const localVarPath = `/api/v1/financial-instruments`;
            // use dummy base URL string because the URL constructor only accepts absolute URLs.
            const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL);
            let baseOptions;
            if (configuration) {
                baseOptions = configuration.baseOptions;
            }

piovra · October 28, 2025, 6:00pm

For reference this is the configuration I am using for code generation:

piovra · October 28, 2025, 7:47pm

If for e.g. I select just the createAccount endpoint and do code get just for that guy, I see the new operation being created, but it deletes all the operations form the same file

piovra · October 28, 2025, 10:07pm

Please let me know about a resolution ETA when you’d have a chance

piovra · October 28, 2025, 10:51pm

Please let me know about a resolution ETA for the above remaining issue.

Apidog Support · October 29, 2025, 1:03am

Understood, we’ll try to reproduce and locate the issue, and will update you once we have a conclusion.

piovra · October 29, 2025, 7:29am

Ok, ty. Please keep me posted as this is blocking our development.

piovra · October 29, 2025, 3:24pm

Any news?

Apidog Support · October 29, 2025, 4:38pm

We apologize, but we haven’t been able to reproduce this issue in similar test scenarios. Both individual and all endpoints generate code containing operationId without missing export content. To help us resolve this faster, could you please provide:

Your Apidog version number
The problematic endpoints exported in Apidog format (share with our staff Emily)
Thank you for your patience!

piovra · October 29, 2025, 5:13pm

We solved the problem for createAccount with these steps:

Duplicate the Create Account endpoint.
Delete the old Create Account endpoint.

These 2 steps allowed generation of the Create Account in code gen with any of the tools we have: Rust or Typescript.

The Old Create Account was at the top in the folder it was sitting in. If we tried to put the new/duplicated Create Account also at the top of the folder in our dev branch. The codegen stopped working. If that helps you on your side.

I don’t know where to find the version number for the Desktop Client. Where is it?

I will try soon the same steps with Create Financial Instruments and keep you posted.

piovra · October 29, 2025, 5:30pm

So, for the Create Financial Instrument, we just took the shorter route:

Just moved the enpoint from the top of the folder to the bottom and the endpoint got included in codegen - i.e. no duplicate and delete

Apidog Support · October 30, 2025, 11:21am

This link is now working normally: Vulcan Forge