Building a High-Performance OpenAPI Parser in Go

Re:Building a High-Performance OpenAPI Parser in Go by ryanackley on Thursday December 18, 2025 @04:24AM (#46310556)

One observation I've had recently. Postman files seem more popular the OpenAPI specs lately. Major SaaS companies will produce a postman file but not an OpenAPI spec. Two examples: Salesforce and Notion

This is really unfortunate because Postman requires you to have an account and log in to download or export these to another format.

Prediction: Postman produces a paid MCP for API lookup in the near future

[ Parent | on HN ]

Re:Building a High-Performance OpenAPI Parser in Go by Raed667 on Thursday December 18, 2025 @06:54AM (#46311587)

I just wanted an API client with some basic features:

- history

- grouping/folders

- some very basic api key management

Is that too much to ask or does every company need to indefinitely grow?

[ Parent | on HN ]

Re:Building a High-Performance OpenAPI Parser in Go by fathead_glacier on Thursday December 18, 2025 @07:50AM (#46312029)

Bruno ticks the boxes for this https://www.usebruno.com/

No affiliation, just a long term fan after years of frustration with Postman and Insomnia.

[ Parent | on HN ]

Re:Building a High-Performance OpenAPI Parser in Go by throw-12-16 on Thursday December 18, 2025 @06:33AM (#46311448)

Postman is my goto example for saas enshitification.

Something that should have just stayed foss.

[ Parent | on HN ]