Automated data mapping that integrates with any pipeline

Chances are your business partners work with different data schemas than you do. With Mappings, that’s no longer a problem. Using our uncluttered UI, you can build a mapping definition quickly and after that, you can use the API to map data into the shape you need without extra effort.

Start Mapping

Same data, different shape

With Mappings you can express complex transformations without it turning into a mess of lines and arrows. Once you've defined your mapping, you can apply it to any incoming or outgoing document automatically.

Uncluttered UI

Mappings focuses on showing you the data you need when you need it. You won't be confused by all the lines and shapes that are part of fields that you're not working on right now.

Powerful mapping language

A mapping definition is based on a series of expressions. The language you use for these expressions supports any data transformation you need.

Not just for programmers

You don't need a course in programming to use Mappings. If you've worked with a spreadsheet before, you'll have no trouble defining a mapping.

Easy to learn

Autocomplete and documentation tooltips make it easy to discover all features Mappings has to offer and they keep writing mappings understandable, no matter your level of experience.

Integrates with your tech stack

It doesn't matter what technology you use: as long as you can send HTTP requests, you can map your documents using Mappings.

API Reference

100% pay-per-use

No upfront fees, no monthly commitments, no user licenses; you only pay for the data that you map. We also have a generous free tier to try it out first.


Works for JSON, EDI, CSV and XML

Mappings can work with any JSON document and turn it into whatever shape you want.

If your data is in EDI, you can use EDI Core to translate it to JSON first. Need to process CSV or XML? Converter has you covered.

You don’t have to build it from scratch. Take a look at these examples to get started quickly.

Easily map a Stripe Charge object to the QuickBooks SalesReceipt object.

View code on GitHub

Easily map a JEDI 846 Inquiry/Advice to the Shopify Inventory Level API object.

View code on GitHub
View more Mappings examples

Write mappings with JSONata

Defining a mapping requires a language that keeps the simple things simple and makes the difficult things possible. JSONata does exactly that. It isn’t hard to learn, either; it just takes some practice. That’s why we have the JSONata Playground. Play around, learn quickly, and share your examples.

JSONata Playground

Ready to dive in?

Sign up to get an API key and start building your own solution.

Sign up

Want to learn more?

We’d love to learn about your use case and show you around.

Book a demo

Subscribe for updates

Get the latest product updates and blog posts delivered to your inbox.

About Stedi

We’re solving EDI

EDI is hard; we know that. It’s an old, technical solution to a modern, logistical problem. It’s connecting businesses on a global scale by tying them together through technical details. It’s what we have and it isn’t going away.

So, we’re here to make it better. We’re here to make it so good that all the world’s EDI transactions can run on Stedi and you wouldn’t know or care, because it works. That’s why we’re here. That’s what we do. That’s Stedi.

EDI CoreMappingsConverterPricing
  1. Twitter
  2. GitHub
Backed by
AdditionBloomberg BetaFirst RoundStripeUSV
System StatusCustomer AgreementService TermsPrivacy Notice

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.