Identify your current integration
The existing Transform operations guide documents the earlier API workflow. Get started with the Unstructured Transform MCP server documents connecting an AI tool.Compare your current integration with /api/v2
These guides describe /api/v2 requests. Completed HTTP 200 submission responses return document fields at the top level. An HTTP 202 response contains an accepted job, and job retrieval wraps the completed document in result. Compare your existing requests and consumers with the API reference before changing them.
If you already have an API key authorized for the target Transform environment, reuse it when calling these endpoints. Send it in the unstructured-api-key header as described in authentication; you do not need to create a new key solely because you are using /api/v2.
Keep your existing integration on its documented path while you compare it with /api/v2. Review the request and response shapes in the API reference, then update your consumer for any contract differences before switching.