Version 9 vs Version 10 - A Comparison

Both v9.x.x and v10.x.x use the same parsing engine under-the-hood!. Version 10 is 90% simpler, more streamlined, and has SDKs available to help build out your integration.

So what is different in v10?

For Version 10 of our API (its not a new parsing engine version), we focused on simplifying how you send data to the API and the format of data you receive from the API. Take a look at the examples below to understand that, for v10, only the format of the data changes, not the data itself:

API Object	Version 9	Version 9 Problem	Version 10	Version 10 Resolution
The 'ParsedDocument' in a parse response		This is a string-encoded JSON object, so it is difficult to read and must be parsed as JSON before you can consume it in your application.		This is a JSON object, so it is much more simple to browse the raw response and consume in your application.
JSON property names and values		The JSON property names contain : and @. The JSON values are all strings (even the integers and booleans).		The JSON property names are much better suited for consumption in a variety of programming languages. There is no need to parse integer and boolean values from strings.