# Prudential Developers

Prudential developer API documentation

## Documentation
- [Home](/home.md)
- [Getting Started](/getting-started.md)
- [Get Access](/get-access.md)
- [API Environments](/api-environments.md)
- [API Access](/api-access.md)
- [API Access with KONG](/api-access-with-kong.md)
- [API Design Standards](/api-design-standards.md)
- [Versioning](/versioning.md)
- [Changelog](/changelog.md)
- [Agent Validation](/can-i-sell-validation-api/agent-validation.md) - Agent Validation. <p>This API will determine the appropriate distribution selling chain for a producer looking to sell a specific product to a client.  The API request body provides various fields that can be used to identify the advisor and various fields to identify the General Agency that they are selling through and the Firm if one is involved.  It also includes request data that identifies the information key to performing the validation such as the product being sold, the state it is being sold in and the resident state of the person being insured.  Based on the distribution selling chain determined, all of the validations that need to be performed will occur and any requirements that are not in good order will be provided in the API response.</p>
- [Get product rules](/product-rules-api/get-product-rules.md) - Get product rules. <p>Get product rules based on customer information and/or productId</p>
- [Generates quotes for a given product](/quotes-api/generate-quotes.md) - Generates quotes for a given product. <p>Generate quotes for a product based on certain customer information</p>
- [Create an Application](/new-business-applications-api/create-application.md) - Create an Application. <p>Starts new business application creation process by performing product eligibity, license and validation if agent is involved, customer creation etc.,</p>
- [Get details of an application](/new-business-applications-api/get-application-details.md) - Get details of an application. <p>provides point-in-time details of an application as it goes through different stages</p>
- [Retrieve all quotes generated for an application](/new-business-applications-api/retrieve-quotes-for-application.md) - Retrieve all quotes generated for an application. <p>Fetch all quotes data generated for an application</p>
- [Generate quotes for an application](/new-business-applications-api/generate-quotes-for-application.md) - Generate quotes for an application. <p>Generate quotes for an application</p>
- [Retrieve previously selected quote details](/new-business-applications-api/retrieve-selected-quote-for-application.md) - Retrieve previously selected quote details. <p>Retrieve previously selected quote details</p>
- [Save selected quote for a given application](/new-business-applications-api/save-selected-quote-for-application.md) - Save selected quote for a given application. <p>Save selected quote for a given application from the set of generated quotes</p>
- [re generate quote by changing values such as face amount and coverage duration](/new-business-applications-api/regenerate-quote.md) - re generate quote by changing values such as face amount and coverage duration. <p>This API provides the flexibility to re-generate a quote for an application_id after Underwriting is completed. This is applicable only for SIFE and SILT products at this point of time.</p>
- [Consent Status](/document-management-api/consent-status.md) - Consent Status. <p>Retrieves the current status of consent document authorization and submission. If no documents have been generated yet then this call will start the process.</p>
- [Consent Submission](/document-management-api/consent-submission.md) - Consent Submission. <p>Submits authorized consent documents to the application</p>
- [Policy Package Signature](/document-management-api/policy-package-signature.md) - Policy Package Signature. <p>Performs actions required to sign Policy Package documents</p> <p>There are several different behaviors of this operation, depending upon the current state of signing and whether optional URL parameters have been supplied...</p> <ol> <li>If Policy Package signing has yet to be started... <ul> <li>If payment has not yet been received, an error will be returned due to a conflict between lack of payment and the attempted signature operation</li> <li>If payment has been received, signing will be initialized with a signing initiation email sent to the first signer</li> </ul> </li> <li>If Policy Package signing has been started - and no optional URL parameters have been supplied - real-time synchronization with the signing vendor will be performed <ul> <li>While inbound signing status events are expected from the signing vendor within a minute or two of any signing action, they may be delayed or, potentially, fail to be received</li> <li>This synchronization feature will perform real-time polling of the signing vendor for status, providing the very latest signing status without having to wait for any inbound signing status event</li> <li>This is as opposed to the Policy Package Status operation, which is a lighter-weight operation that will provide the list of documents and report the latest known signing status without any attempted synchronization</li> </ul> </li> <li>If Policy Package signing has been started, and the optional <code>resend</code> URL parameter is supplied, a signing initiation email is re-sent to the current signer <ul> <li>Note: A signer may enter their access code incorrectly too many times resulting in being locked out of signing, in which case re-sending the email will also serve to unlock signing; re-enabling the signing link in both new and prior signing initiation emails</li> </ul> </li> <li>If Policy Package signing was systematically voided or declined by an individual signer, and the optional <code>reset</code> URL parameter is supplied, signing will be re-initialized with a signing initiation email sent to the first signer</li> <li>If Policy Package signing was successfully completed but authorized documents not yet submitted, the request is a NOP with a reminder that the documents are authorized and ready to be submitted</li> <li>If Policy Package signing was successfully completed and authorized documents already submitted, the request is a NOP with a message that the documents are both authorized and submitted</li> </ol> 
- [Consent Signature](/document-management-api/consent-signature.md) - Consent Signature. <p>Performs actions required to sign Consent documents</p> <p>There are several different behaviors of this operation, depending upon the current state of signing and whether optional URL parameters have been supplied...</p> <ol> <li>If Consent signing has yet to be started, it will be initialized with a signing initiation email sent to the first signer</li> <li>If Consent signing has been started - and no optional URL parameters have been supplied - real-time synchronization with the signing vendor will be performed <ul> <li>While inbound signing status events are expected from the signing vendor within a minute or two of any signing action, they may be delayed or, potentially, fail to be received</li> <li>This synchronization feature will perform real-time polling of the signing vendor for status, providing the very latest signing status without having to wait for any inbound signing status event</li> <li>This is as opposed to the Consent Status operation, which is a lighter-weight operation that will provide the list of documents and report the latest known signing status without any attempted synchronization</li> </ul> </li> <li>If Consent signing has been started, and the optional <code>resend</code> URL parameter is supplied, a signing initiation email is re-sent to the current signer <ul> <li>Note: A signer may enter their access code incorrectly too many times resulting in being locked out of signing, in which case re-sending the email will also serve to unlock signing; re-enabling the signing link in both new and prior signing initiation emails</li> </ul> </li> <li>If Consent signing was systematically voided or declined by an individual signer, and the optional <code>reset</code> URL parameter is supplied, signing will be re-initialized with a signing initiation email sent to the first signer</li> <li>If Consent signing was successfully completed but authorized documents not yet submitted, the request is a NOP with a reminder that the documents are authorized and ready to be submitted</li> <li>If Consent signing was successfully completed and authorized documents already submitted, the request is a NOP with a message that the documents are both authorized and submitted</li> </ol> 
- [Policy Package Status](/document-management-api/policy-package-status.md) - Policy Package Status. <p>Retrieves the current status of policy package document authorization and submission. If no documents have been generated yet then this call will start the process.</p>
- [Document Streaming Or Detail (varied by 'Accept' header content negotiation)](/document-management-api/document-streaming-or-detail-1.md) - Document Streaming Or Detail (varied by 'Accept' header content negotiation). <p>Streams (Accept: 'application/pdf'), or provides detail of (Accept: 'application/json'), a consent or policy package document associated with an application</p>
- [Initiating the process for Interview](/interview-api/initiate-interview.md) - Initiating the process for Interview. <p>This endpoint is to initialize the interview by providing the required information to start the process.</p>
- [Obtain Questionnaire information for underwriting for LT/DT and SIFE Products](/interview-api/get-interview-questionnaire.md) - Obtain Questionnaire information for underwriting for LT/DT and SIFE Products. <p>It will produce a list of questions and validations in JSON form for LT/DT and SIFE Products</p>
- [Submit questionnaire data for underwriting](/interview-api/submit-interview-underwriting.md) - Submit questionnaire data for underwriting. <p>Submit Customer Questionnaire Form Data to this endpoint to send for underwriting</p>
- [Attempt to place a policy in force](/policy-placement-api/policy-placement.md) - Attempt to place a policy in force. <p>POST Call for Placing a Policy</p>
- [Post Lookup Application](/application/post-lookup-application.md) - <p>Lookup details of a New Business Life Insurance application</p>
- [Create Quote](/core-quotes-api/create-quote.md) - <p>Create a Quote for Provided Customer Criteria</p>
- [Create Projection](/core-projections-api/create-projection.md) - <p>Create a Projection of a given product type based on the provided customer information</p>
- [Get Products By Group And State](/core-product-rules-api/get-products-by-group-and-state.md) - <p>Get Products List for all Life Products and Filter using Resident State and Product Group</p>
- [Get Core Product Rules](/core-product-rules-api/get-core-product-rules.md) - <p>Gets all of defined Rule Criteria for the given product</p>
- [Agent Validation](/agent-validation/agent-validation.md) - Agent Validation. <p>This API will determine the appropriate distribution selling chain for a producer looking to sell a specific product to a client.  The API request body provides various fields that can be used to identify the advisor and various fields to identify the General Agency that they are selling through and the Firm if one is involved.  It also includes request data that identifies the information key to performing the validation such as the product being sold, the state it is being sold in and the resident state of the person being insured.  Based on the distribution selling chain determined, all of the validations that need to be performed will occur and any requirements that are not in good order will be provided in the API response.</p>
- [Process Transmission](/enrollment-api/process-transmission.md) - <p>Creates a transmission containing a single payload of an enrollment or eligibility record.</p>
- [Check Application Status](/status-check/check-application-status.md) - Check Application Status. <p>Retrieves the status and application details of an annuities new business application for a given application number.</p>
- [Submit Completed Training](/training-completion/submit-completed-training.md) - Submit Completed Training. <p>Submit training details for a course that an agent has completed.</p>
- [Agent Can Sell Validation](/producer-validation/agent-can-sell-validation.md) - Agent Can Sell Validation. <p>Performs a can sell check on the agent to confirm if they have the necessary licensing, appointment, and training.  The response will indicate if the agent can sell or if they cannot sell.  If they cannot sell a list of reasons will be returned in the response.</p>
- [Fetch annuities contract details](/get-annuities-contract-by-id/get-annuities-contract-by-id.md) - Fetch annuities contract details. <p>Fetch details for the requested annuities contract</p>