Zinnia Market Connect Order Entry API - server-driven order entry for life and annuity products.
Overview
The API exposes the order entry blueprint (sections, subsections, fields, validation, visibility) and the data captured against it. Clients render the blueprint with the Zinnia Form Engine SDK and submit answers back through the Transaction endpoints.
Authentication
All endpoints require a JWT bearer token in the Authorization header (Authorization: Bearer {token}). Tokens are issued by Auth0; contact your Zinnia onboarding representative for credentials.
Base URLs
- Development:
https://dev.api.zinnia.io - QA:
https://qa.api.zinnia.io - UAT:
https://uat.api.zinnia.io - Production: provided per integration agreement
Versioning
The API is versioned in the path (/market-connect/order-entry/v1/...). Breaking changes are released under a new major version segment; non-breaking additions ship within the existing version.
Error Handling
Errors follow the ErrorResponse schema with a stable code (see ErrorInfo.code enum), a human-readable description, optional details, and a timestamp. Application-level failures are also surfaced in the errors array of TransactionResponse for endpoints that return 200 with partial success.
Getting Started
- Acquire a JWT token from Auth0.
POST /market-connect/order-entry/v1/transactionwithstateandcusipto create a transaction.GET /market-connect/order-entry/v1/transaction/{transactionId}to fetch the blueprint and data.PUT /market-connect/order-entry/v1/transaction/{transactionId}/{stepName}to save answers and advance.POST /market-connect/order-entry/v1/transaction/{transactionId}/submitto submit the completed transaction.
- Server 1:https://dev.api.zinnia.io
- Server 2:https://qa.api.zinnia.io
- Server 3:https://uat.api.zinnia.io
bearerAuth (http)
JWT bearer token issued by Auth0. Send as: ‘Authorization: Bearer {token}’.