Zinnia EAPP API specification for annuity products. All these services support oAuth.
QA Environment
DEV Environment
Production Environment
EAPP API Version 1
This will be passed as Bearer plus “token” as generated by above token API.
Example:Bearer eykjsfjfjasdasdad
Details required to submit the eApp to Zinnia for Annuity
Date (with pattern “yyyy-mm-dd”). e-App submitted date to Zinnia.
Example:2023-12-19
An identifer that represents Transmitting Company
Transmitting Company Name
Receiving Company Name
Example:ARCUS
External ID in MCS that belongs to the Firm
Date (with pattern “yyyy-mm-dd”). Agent submit date.
Example:2023-12-19
Application Signed County
Product code assigned by Zinnia Admin system
Example:111
Application Status code derived at Zinnia
Example:App Entry
Application Signed Date (with pattern “yyyy-mm-dd”).
Example:2023-12-19
Client Agreement Date/Issue Date (with pattern “yyyy-mm-dd”).
Example:2023-12-19
The date in which the Agent first proposes to the client the use of an insurance product, which may or may not be in response to an engagement/planning process. (with pattern “yyyy-mm-dd”).
Example:2023-12-19
The start (run) date of the illustration or quote (with pattern “yyyy-mm-dd”).
Example:2023-12-19
This date represents when the natural owner electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Example:2023-12-19
This date represents when the joint owner electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Example:2023-12-19
This date represents when the Annuitant electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Example:2023-12-19
This date represents when the joint Annuitant electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Example:2023-12-19
This date represents when the trustee/representative electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Example:2023-12-19
This date represents when the Beneficiary electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Example:2023-12-19
This date represents when the Spouse electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Example:2023-12-19
Stores the IGO date. It is mandatory when contract have trust Date (with pattern “yyyy-mm-dd”). Derived by Zinnia.
Example:2023-12-19
Unique Identifier against an e-App application. First two letters represent the receiving company, next 3 letters represent the firm, next 8 positions represent the date eApp is submitted, next 10 positions represents the sequential number of the eApps from the eApp instance.
Example:XXEDJ041120240000000001
Version for that case - 3 digits, incremental if same case if submitted more than once in case of errors.
Example:000
Contract State. 2 Digit state code
Example:NJ
Qualification Codes
Allowed values:123456789111314161718192021222324252627282930313233343536373839404156575859
To determine whether the request is via eApp or Paper App
Allowed values:EP
Commission Options will be provided by Zinnia for the respective Product
Example:A
imoFlag Derived at Zinnia
Allowed values:YesNo
Brokerage Identification Number
Roth year - Derived by Zinnia
Example:2024
Tele privileges value
Allowed values:123456
funds that sums upto 100% or the total dollar values sums to the grossAmount
>= 1 items
feature for any feature/rider selected by user
>= 1 items
roles that sums every role option to 100%
>= 1 items
specialPrograms if any recurring transaction needs to be set up
>= 1 items
payouts if it needs to be set up for the policy
Accepted
Example:201
Example:Request Submitted Successfully