Sources and scanning
Why is an endpoint missing after a scan?
The scanner reads route definitions from code. When an endpoint you expect isn’t in the catalog, one of these is usually the reason.
Check the branch: a repository is read on one branch. Add it again on another branch if that’s what runs where you test.
Check the framework: Express, NestJS, Fastify, Hono, Elysia, Laravel, Symfony, Django, Rails, Spring, ASP.NET Core, Go routers and more are read. Routes built at runtime from configuration can’t be seen in code.
Check prefixes: a global prefix or a router mounted under a path is followed where the scanner can see it. If paths come out without their prefix, add the prefix to the environment’s API URL.
Choose Scan again after a push: scans don’t run on every commit.
If it still misses routes, add an OpenAPI document: it gives the exact catalog.
Didn’t answer your question? Contact support.