InstaBrain Developer Documentation Schedule for SDK and Integration Partners
Version 2026-09-08. Effective September 8, 2026. This page is the versioned developer documentation that the InstaBrain Terms of Use for SDK and Integration Partners incorporate for the fields listed in section 14.4 of those terms: the operational limits under section 3, the designated security and notice contacts under sections 7 and 14.1, the template applicant notice language under section 6, and the list of transaction-related system messages and the allocation of tasks for them under section 11. The version of this page in effect when a Partner accepts the terms is recorded with that Partner's Technical Questionnaire response. Technical specifications for the APIs themselves are published separately in the InstaBrain API documentation supplied at onboarding.
1. Designated contacts
Security contact (terms section 7). A Partner's security incident notice goes by email to [email protected]. State what happened, what data and credentials are affected, what containment is in place, and who at Partner to contact.
Notice contact (terms section 14.1). Legal and contractual notices to InstaBrain go by email to [email protected]. The courtesy postal copy goes to the address shown on the InstaBrain Contact page.
Technical support. Integration questions and defect reports go to [email protected]. Technical support is not a notice route under the terms.
2. Published service limits (terms section 3)
The limits published in this version are the endpoint limits below. Partners implement retries with backoff for critical calls, honor the retry interval a 429 response states, in the Retry-After header or the response body, and do not run tight retry loops.
| Endpoint | Limit | Response when exceeded |
|---|---|---|
| GET /api/ThirdPartyApplication/final-submit-status | 1 request per 2 seconds per opportunityId | 429 Too Many Requests with a Retry-After: 2 header |
| GET /api/ThirdPartyPayment/cc-payment-status | 1 request per 10 seconds per opportunityId | 429 Too Many Requests, body "Too many requests. Retry after 10 seconds." |
No other concurrency or request limit is published in this version. Additional default limits may appear in a later dated version of this page and take effect under section 3 of the terms.
3. Template applicant notice language (terms section 6)
Partner may use the following template, adapted to its interface, as part of the disclosures and authorization language it presents before collecting applicant information. Where Partner's interface operates on behalf of another entity under section 4 of the terms, name that entity in place of, or alongside, Partner's name. Using the template does not by itself satisfy section 6; Partner remains responsible for the disclosures, consents and authorizations applicable law requires for its own collection and submission.
The information you provide in this application will be used and shared by [Partner name], InstaBrain, and the insurance carrier whose product you are applying for, together with their service providers, to determine eligibility, underwrite your application, prevent fraud, meet legal and regulatory requirements, contract for and service your policy, and keep the application secure. The insurance carrier, not [Partner name] or InstaBrain, decides whether to approve, decline or issue a policy and on what terms. By continuing you confirm that the information you provide is accurate and complete and you authorize this use and sharing.
4. Transaction-related system messages (terms section 11)
The platform sends the transaction-related messages catalogued below by email or SMS. For each message the table states the channel, the recipient, the trigger, and the party that performs the trigger, recipient and content tasks and the consent and opt-out tasks. In this version the same party performs both sets of tasks for every message. Where a message is sent at Partner's direction or because Partner started, configured, requested or enabled it, Partner performs those tasks. Where a message is sent on the platform's own trigger or at a carrier's direction, the party named below performs them. This catalogue allocates tasks between the parties; it does not determine the statutory status of any message.
How to read the table. Messages are identified by the first eight characters of the template identifier used in the platform. The trigger column describes the event that fires each message, read from the platform's message templates as exported on 2026-08-14. Where a cell names an underwriting or issuance event, that event is the carrier's decision under section 11 of the terms; the platform transmits it. "InstaBrain" means the message is sent on the platform's own trigger or on a carrier decision, and InstaBrain performs the trigger, recipient and content tasks and the consent and opt-out tasks for it. "Partner if note 1 applies; otherwise InstaBrain" means the allocation follows note 1 below the table. Internal operational alerts and messages of the InstaBrain agent portal are not part of a Partner integration and are not listed.
| Ref | Message | Channel | Recipient | Trigger | Party performing the trigger, recipient, content, consent and opt-out tasks |
|---|---|---|---|---|---|
| BE0CEFC8 | Email verification code | Applicant | Applicant enters an email address to be verified during the application | Partner if note 1 applies; otherwise InstaBrain | |
| AC11B0B7 | Mobile verification code | SMS | Applicant | Applicant enters a mobile number to be verified during the application | Partner if note 1 applies; otherwise InstaBrain |
| 69312B0C | Application authorization invitation | Applicant | Agent invites the applicant to authorize the application | Partner if note 1 applies; otherwise InstaBrain | |
| 39CEFF2F | Application authorization link | SMS | Applicant | Agent invites the applicant to authorize the application | Partner if note 1 applies; otherwise InstaBrain |
| 59BA6C8D | Final quote authorization link | SMS | Applicant | Agent sends the applicant a link to the application | Partner if note 1 applies; otherwise InstaBrain |
| DB115857 | Application session link | SMS | Applicant | Agent invites the applicant to join a live application session | Partner if note 1 applies; otherwise InstaBrain |
| 7FD87E44 | Offline application link | Applicant | Agent sends the applicant a link to complete the application on their own | Partner if note 1 applies; otherwise InstaBrain | |
| 2C89AA9A | Application completion reminder 1 | SMS | Applicant | Application started and not completed; first reminder | Partner if note 1 applies; otherwise InstaBrain |
| 40BD198C | Application completion reminder 2 | SMS | Applicant | Application still pending; second reminder | Partner if note 1 applies; otherwise InstaBrain |
| 884B8E34 | Application completion reminder 3 | SMS | Applicant | Application still pending; final reminder | Partner if note 1 applies; otherwise InstaBrain |
| F4E8A1C2 | Continue later link | SMS | Applicant | Applicant chooses to continue the application later | Partner if note 1 applies; otherwise InstaBrain |
| 4FFCEB9D | Welcome and application recovery | Applicant | Application partially completed | InstaBrain | |
| C025F048 | Signing reminder | Applicant | Application awaiting the applicant's signature; states the signing window after which the application is abandoned and refunded | Partner if note 1 applies; otherwise InstaBrain | |
| B3459C7D | Processing delay resolved | Applicant | A processing delay on the application date is resolved; applicant invited to resume | InstaBrain | |
| 2B84E0C8 | Application ready to complete | SMS | Applicant | A processing delay is resolved; applicant invited to pick up where they left off | InstaBrain |
| 091410A3 | Processing error | Applicant | A system outage prevented the application from completing; applicant invited to start a new one | InstaBrain | |
| 91D9F9BB | Decision after processing: declined | Applicant | The application is declined in underwriting after processing; the message states the reason provided | InstaBrain | |
| 33031930 | Decision: declined | Applicant | The application is declined in underwriting; the message states the reason provided | InstaBrain | |
| A8A62BE5 | Decision: declined | SMS | Applicant | The application is declined in underwriting; applicant referred to the agent | InstaBrain |
| C0E48D08 | Application closed after manual review | Applicant | An underwriter closes the application after manual review | InstaBrain | |
| BB1320F1 | Application closed after manual review | SMS | Applicant | An underwriter closes the application after manual review; applicant referred to the agent | InstaBrain |
| EE756A5B | Alternative coverage options | Applicant | The product applied for is not approved in underwriting; alternative products offered | InstaBrain | |
| EABFEFCF | Quote expired on age change | Applicant | Applicant's age changed after the final quote was accepted; pricing must be recalculated | InstaBrain | |
| EC7898F2 | Application abandoned and refund started | Applicant | Signing not completed in the signing window; application abandoned and any payment refunded | InstaBrain | |
| 68FB9A64 | Pay Later acknowledgment | Applicant | Application received with a deferred payment date; states the amount and draft date | InstaBrain | |
| DB75F3F4 | Application authorized | Agent | Applicant authorizes the application | InstaBrain | |
| 67726F11 | Agent signature required | Agent | Applicant completes the application; agent signature required | InstaBrain | |
| 10CF9A15 | Complete the sale | Agent | A saved application is ready for final completion | InstaBrain | |
| BF5857C1 | Policy issued | Agent | The policy is issued; the message states the policy number | InstaBrain |
Note 1. Partner performs the tasks for a message if Partner started the message, configured, requested or enabled it through the platform, or directed the platform to send it, including where Partner's integration or a user of Partner's interface did so. Otherwise InstaBrain performs them.
The platform supplies the text of each message and addresses it to the applicant or agent on the application record. A Partner that starts a message accepts that text and addressing as its content and recipient for section 11. Changes to this catalogue are published as a new dated version of this page.
Messages to Partner's own developers. Listed for completeness; they are not applicant or consumer contact and no section 11 task is allocated for them. 1A2EE709, email, one-time sign-in code when a Partner developer signs in to the developer portal. CE7D3023, email, acknowledgment sent when a Technical Questionnaire is submitted, carrying the sandbox credentials and the steps to production.
5. Version history
2026-09-08. First published version. Contacts designated, two endpoint limits published, applicant notice template supplied, system message catalogue published (29 applicant and agent messages, plus two developer messages).
Version 2026-09-08. Effective September 8, 2026. Questions about this page go to [email protected].