Skip to content

Comment on Translate Between JSON and EDI

Comments

a new API for creating and validating EDI files that conform to precise trading partner specifications

Unless you can host this locally this seems like a deal breaker in many industries (healthcare, insurance and perhaps others)

Even after the contracts being signed to make it complient, it was the pricing for what it is that gets us. It would be cheaper to write our own translation tool for our specific needs after 3 months of usage, and we are at a smaller scale than most for api calls.

Not sure which sweet spot they want to hit with this

What sort of scale? Would love to see the math. (Context: I'm the CEO – if our pricing doesn't make sense for certain use cases, I'd love to dig into it)

We have lots of customers in regulated spaces – healthcare is a big one – but it's definitely a dealbreaker for certain companies that have hard rules for running everything in their own environments.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.