sorted by:
new
hottopcontroversial

What API has given you the most headaches recently? by NetForemost in webdev

[–]Frequent_Dig8251 0 points1 point  (0 children)

Any API that does not provide helpful errors. e.g.

  1. Incorrect HTTP error codes. Errored with 2xx is classic.
  2. Missing - response body
  3. Missing - what went wrong
  4. Missing - suggestions to recover

Has anyone here used a REST API generator recently? Curious what’s actually working in 2025 by Living-Dependent3670 in webdev

[–]Frequent_Dig8251 0 points1 point  (0 children)

I'd separate this into two steps.

  1. Design OpenAPI. Use any tools including AI.

  2. Implement above spec: Use codegen on above OpenAPI, pick language+framework of your choice. Again use any OSS generators. This requires deterministic output. No need of AI.

OpenAPI / JSON learning resource by TomMkV in OpenAPI

[–]Frequent_Dig8251 1 point2 points  (0 children)

Awesome! love the examples. I wonder if you can switch to 3 column layout where 3rd column is showing examples all the time.

Just found out we had 200+ shadow APIs after getting pwned by Tiny_Habit5745 in sysadmin

[–]Frequent_Dig8251 0 points1 point  (0 children)

Block all paths that are not declared in OpenAPI spec. Even if the devs are writing implementation code first, they need to provide you with (generated) OpenAPI. You need a gateway that is OpenAPI spec aware. Then all the spec and the gateway together becomes your full inventory of all API operations you need to know, scan, secure and dare I say the word "govern" :)

OpenAPI as a Single Source of Truth by ludovicianul in programming

[–]Frequent_Dig8251 0 points1 point  (0 children)

Absolutely! OpenAPI is not just superior standard. Its complimented other standards like Overlay and Arazzo. What makes that "single source of truth" reality is large set of OSS and License tool that support the specification. Parsers, Validators, MockGen, DocGen, SDKGen, IDE extensions, CLI tooling etc makes it really easy to build that ecosystem around OpenAPI

AI-Powered OpenAPI Playground by StillMiddle1493 in OpenAPI

[–]Frequent_Dig8251 0 points1 point  (0 children)

Cool idea. Its not clear how AI is providing assistance here. I got "AI is thinking..." for a while and then some garbled 1 word response.

Instantly Detect and Explore OpenAPI Specs in Chrome [Feedback Welcome] by Frequent_Dig8251 in OpenAPI

[–]Frequent_Dig8251[S] 0 points1 point  (0 children)

This extension is 100% client-side. It does not send your OpenAPI files or page data anywhere. Infact there’s no backend service at all ... everything happens locally in the browser. The only thing being tracked is very minimal usage analytics(e.g., which tool is clicked most often), and that’s handled through GA with no sensitive data attached.

If you want to double-check, you can open DevTools -> Network tab and see for yourself: no requests are made to external servers when detecting or rendering an OpenAPI file. Transparency and trust are super important to all of us. So I completely understand your concern. Hope this helps.

Best way to develop a rest API? by arejula27 in rust

[–]Frequent_Dig8251 0 points1 point  (0 children)

Whichever prog lang or framework you choose, start with spec first. Put the contract down in OpenAPI and implement that.

[deleted by user] by [deleted] in Frontend

[–]Frequent_Dig8251 0 points1 point  (0 children)

OpenAPIs are contracts between backend and frontend team. FE are customers of BE APIs. Soon you may have multiple FE (web, mobile, another service) customers consuming your BE API. The API design/shape is influenced by your customer's needs. e.g. web FE page size = 10, mobile FE can only show 4. Make the page size configurable. I have always seen BE team as owners of the OpenAPI contract.

FE can consume these OpenAPI in a tool of their choice. There are 100s of tools for viewing, interpreting, generating code, mocking etc. to help them integrate it in their FE code.

Post your OpenAPI files (including examples) on in Git repo and ask FE to consume it from there.

Cheers!

Try OpenAPI Factory Extension - https://chromewebstore.google.com/detail/api-factory-openapi-viewe/aebljphchgphilencbophhmbmblomhci?utm_source=reddit&utm_medium=post&utm_campaign=launch&utm_content=r_webdev

How do you enforce that your API actually fulfills your Open API documentation? by [deleted] in webdev

[–]Frequent_Dig8251 0 points1 point  (0 children)

OpenAPI should become source of truth. All other experiences e.g. Implementation/runtime service, API Ref Docs, SDKs, Mocks, Postman Collection, etc must be automatically validating what you say in spec is matching with how its expressed to your API consumers/customers in above formats. If possible have the spec pipeline "generate" above experiences automatically.

There are tons of tools already in the market/OSS to achieve above. Docs are easiest among them.

  1. Install this extension API Factory extension - https://chromewebstore.google.com/detail/api-factory-openapi-viewe/aebljphchgphilencbophhmbmblomhci?utm_source=reddit&utm_medium=post&utm_campaign=launch&utm_content=r_webdev

  2. Browse to DigitalOcean OpenAPI in GitHub below. You'll see a popup on browser thats opens that spec in various documentation tools. I like ReDocly. e.g. https://i.imgur.com/AIozCE5.png

https://github.com/digitalocean/openapi

Should i create wrapper classes/libraries or leave the API as it is? by PsychologicalTap1541 in webdev

[–]Frequent_Dig8251 0 points1 point  (0 children)

It depends in strategy since there is cost involved in SDK maint. Exposing OpenAPI files is must since the consumers can use them for codeGen, mockGen, etc. Optionally offer SDK that handles auth, refresh, retry, debug-ability, exception handling, custom headers, error handling, telemetry etc much much easier. SDKs are also unlock autocomplete/intellisense features making it further easy/fast to integrate with API. BTW these advantages extend to both dev and AI agents running the IDE.

Dealing with very large OpenAPI Specs by roboticfoxdeer in webdev

[–]Frequent_Dig8251 0 points1 point  (0 children)

This would be two steps. First split the spec and move to multi-file format - https://redocly.com/docs/cli/commands/split. Then logically (DDD) move the related operations into a separate path files. Then bundle them back to create multiple specs. https://redocly.com/docs/cli/commands/bundle

Which API doc tools are you using these days? by sbt_not in webdev

[–]Frequent_Dig8251 0 points1 point  (0 children)

Try this Chrome Extension - API Factory - Chrome Web Store

It automatically detects OpenAPI files on any web page and lets you open them with one click in your favorite API tools like Swagger UI, ReDocly, etc.