How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zinnia Transaction API

Transaction management operations

Zinnia Transaction API is one of 42 APIs that Zinnia publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 3 paths, and defines 66 schemas. It is described by OpenAPI 3.2.0, at version 1.0.3.

Requests are made against 3 base URLs: https://dev.api.zinnia.io, https://qa.api.zinnia.io, https://uat.api.zinnia.io.

4 operations 3 paths 66 schemas 1 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.3
Base URL
https://qa.api.zinnia.io
Authentication
OpenID Connect
Terms of Service
Resource Areas
1

Authentication & Security 1

Zinnia Transaction API declares 1 security scheme for authenticating requests. It supports OpenID Connect (openIdConnect) discovered at https://login.qa.zinnia.com/.well-known/openid-configuration. By default, every request must be authenticated.

  • openIdConnect — OpenID Connect via Auth0. Clients present a JWT bearer token issued by the tenant in the Authorization: Bearer header.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Transaction 4

Transaction management operations

POST
/market-connect/order-entry/v1/transaction
Create the Order Entry transaction. Routes to appropriate service based on CUSIP
createTransaction body → 201400401403404429500502
GET
/market-connect/order-entry/v1/transaction/{transactionId}
Retrieves the order entry blueprint and its associated responses for a created…
getTransaction 1 param → 200400401403404429500502
PUT
/market-connect/order-entry/v1/transaction/{transactionId}
Update the Order Entry transaction data for enhanced blueprint…
updateTransactionEnhancedBlueprint 1 param body → 200400401403404422429500
POST
/market-connect/order-entry/v1/transaction/{transactionId}/submit
Submit an order entry transaction for processing
submitTransaction 1 param → 200400401403404429500502

Schemas 66

The contract defines 66 schemas that model the data the API accepts and returns. The most detailed are FieldBlueprint (22 properties), PrefillParty (14 properties), SectionBlueprint (13 properties), PrefillPerson (12 properties). Each schema is shown below with its type and property counts.

PrefillProduct
object
6 properties
FieldValidationRule
object
2 properties 2 required
PrefillNameBase
object
6 properties
PrefillMessageInformation
object
11 properties
PrefillOrganization
object
4 properties
TransactionDataQuestionRowsMap
object
Answers keyed by blueprint question id or composite collection field id. Named properties below are representative examples (same keys as the default example);…
1 property
PrefillPerson
object
12 properties
SectionGroupBlueprint
object
3 properties 2 required
ErrorResponse
object
2 properties 2 required
PrefillPartyRole
object
2 properties
SubscriberAction
object
6 properties
Blueprint
object
2 properties 2 required
ValidationErrors
object
One validation message in API shape. Optional properties are omitted in JSON when null (e.g. fieldId is missing or 0).
4 properties
ErrorInfo
object
4 properties 2 required
TransactionResponse
object
7 properties 3 required
SelectOption
object
2 properties 2 required
PrefillOwner
object
5 properties
SubscriberActionPayload
object
2 properties
PrefillPolicyholder
object
4 properties
ValidationConditionGroup
object
2 properties
FieldGroupBlueprint
object
9 properties 2 required
SectionBlueprint
object
13 properties 3 required
SelectOptionsApplicationContext
object
3 properties
QuestionData
object
One row of captured or echoed answer data. Must include id, type, and value (the JSON property value must be present on each row; use JSON null for an empty op…
8 properties 3 required
PrefillParty
object
14 properties
PrefillUser
object
1 property
LocalizedText
object
1 property
RepeatableBlueprint
object
6 properties
FieldBlueprint
object
22 properties 5 required
StateCode
string
US state, territory, or military mail code (2 characters). Uppercase letters only.
ValidationCondition
object
Single validation condition inside a FieldValidationRule. The shape varies by type: matchesRegexCondition uses regex; numberComparisonCondition uses value + op…
5 properties 2 required
PrefillPhone
object
2 properties
LayoutSettings
object
1 property
PrefillRequest
object
12 properties
PrefillUnderwritingDecision
object
1 property
PrefillDuration
object
3 properties
PrefillAgent
object
4 properties
PrefillLicense
object
4 properties
SubscriberResponseValue
object
3 properties
RenderCondition
object
Single condition controlling whether a field/section is rendered.
4 properties 2 required
PrefillEmployee
object
7 properties
Subscriber
object
3 properties
SubscriberResponseHandler
object
4 properties
SubmitTransactionResponse
object
2 properties 2 required
VisibilitySettings
object
2 properties
SubsectionBlueprint
object
11 properties 3 required
PrefillPolicy
object
6 properties
PrefillFlag
object
2 properties
PrefillPartyIdentity
object
4 properties
PrefillCommunication
object
2 properties
PrefillClient
object
2 properties
PrefillReference
object
3 properties
PrefillPlan
object
5 properties
CreateTransactionRequest
object
7 properties 2 required
PrefillAllocation
object
2 properties
PrefillRelationship
object
2 properties
PrefillIllustration
object
2 properties
VisibilityCondition
object
Single condition controlling whether a field/section is visible at runtime.
4 properties 2 required
PrefillAddressBase
object
7 properties
PrefillBeneficiary
object
5 properties
PrefillInsured
object
2 properties
QuestionDataRows
array
All answer rows for one question or composite collection field id. Use index on each row for repeatable collection instances. Each row must include id, type, a…
PrefillPlanOption
object
2 properties
PrefillAddress
object
5 properties
PrefillQuestionAnswer
object
6 properties
PrefillAnnuitant
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zinnia-transaction-api-openapi.yml Raw ↑

Other APIs Zinnia publishes across the network.

Zinnia Annuity Health Check API
Zinnia Annuity Version 1 API
Zinnia Annuity Version 2 API
Zinnia Attachment API
Zinnia Authorization Status Update API
Zinnia Case Instance API
Zinnia Client Case API
Zinnia Comments API
Zinnia Dataset API
Zinnia Details API
Zinnia Documents V2 API
Zinnia Documents V3 API
Where this information came from

This is an independent, third-party profile of Zinnia Transaction API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.