Execute Financial → Spark Arena

Staging requirements

Please send the items below

Send credentials through a secure channel. We do not need production access until staging passes.

1. Payload we will send

submission_status — allowed values UNDERWRITING or APPROVED
product_type — allowed values Term, IUL, Whole Life, Accidental, Health, or Annuity

Accept capitalization and spacing exactly as shown.

Delivery rules

  • Content-Type will be application/json.
  • Every request includes all nine fields shown below.
  • Each submission gets one unique submission_id.
  • Every retry reuses the same submission_id.
  • annual_premium is a positive number without $ or commas.
  • effective_date uses YYYY-MM-DD.
  • state is a two-letter uppercase code.

Copyable example — Underwriting + Term

{
  "submission_id": "ef-7f23d9a1-4c18-4db8-9123-0a57dcd41c80",
  "agent_name": "Jordan Smith",
  "agency": "Execute Financial",
  "submission_status": "UNDERWRITING",
  "product_type": "Term",
  "carrier": "Americo",
  "annual_premium": 1200,
  "effective_date": "2026-08-01",
  "state": "AZ"
}

The example uses UNDERWRITING and Term. We will use the applicable values listed above in each request.

Agency labels — all 22

We will send these labels unchanged. Map aliases on your side.

  1. Execute Financial
  2. Sentinel Financial
  3. Overtime Financial
  4. Catalyst Financial
  5. Outlaw Financial
  6. Status One Financial
  7. Frequency Financial
  8. Paladin Life Group
  9. Impact Financial Group
  10. Uplift Agencies
  11. Ascend Financial
  12. Ladder Financial
  13. True North Financial
  14. Nitehawk Financial
  15. Break Through Financial
  16. Cobra Financial
  17. Daybreak Financial
  18. DIAL U
  19. Noble Tier Group
  20. SZN Financial
  21. Policy Pros
  22. Genesis Solutions

2. What we need from you

  1. Staging access

    Send the full tokenized staging endpoint and separate x-vercel-protection-bypass value through a secure channel.

  2. Changed submission

    Tell us the response code, response body, and record behavior when an existing submission_id arrives with changed data.

  3. Retry rules

    Provide timeout and 5xx retry timing, maximum attempts, 429 Retry-After behavior, production rate limit, and the process for resuming after 410.

  4. Agent identity

    Explain how you separate same-name agents and handle legitimate name changes.

  5. Production

    After staging passes, send a separate tokenized production endpoint, rotation/revocation contact, and rotation-notification process.

3. Next steps

  1. Send the staging information

    Send the staging endpoint and bypass value securely, then answer each item above.

  2. We connect staging

    We connect the integration using the payload and delivery rules on this page.

  3. We test the full flow

    We test both statuses, all six products, agency values, duplicate protection, retries, and response handling.

  4. We confirm staging results

    We confirm the submitted records and leaderboard totals are correct.

  5. Send production access

    After staging passes, send the separate production endpoint securely.

  6. We connect production

    We complete the production connection and confirm the first live submissions.