Agencies are clamoring for "open APIs" from #insurance carriers, insurtechs, incumbent AMS systems, etc.... but very few are ready or able to effectively integrate. Here's our checklist when working with a new API partner. (P.S. we only work with carriers who have open APIs)
1. API documentation for all Personal Lines P&C (schema, example requests, example payloads)
Business/SME: Responsible for gathering documentation and placing in shared folders.
Tech: Responsible for verifying documentation contains details needed to do integration.
Business/SME: Responsible for gathering documentation and placing in shared folders.
Tech: Responsible for verifying documentation contains details needed to do integration.
2. Coverage Abbreviation codes used by API documentation identified
Business: Responsible for gathering docs that outline coverage abbreviation and supported coverage amounts.
Tech: Responsible for checking coverage abbreviation and amounts are valid with API documentation.
Business: Responsible for gathering docs that outline coverage abbreviation and supported coverage amounts.
Tech: Responsible for checking coverage abbreviation and amounts are valid with API documentation.
3. Provide carriers a list of our IPs to whitelist
Business: When applicable; responsible for providing IP Allow list to carrier and receiving confirmation IPs have been allowed.
Business: When applicable; responsible for providing IP Allow list to carrier and receiving confirmation IPs have been allowed.
4. Request examples of test user data to use in pre-prod testing
Business: Responsible for gathering test data and is responsible for validating test data works in Carrier’s preproduction Agent portal.
Tech: Responsible for validating the test data works in the API.
Business: Responsible for gathering test data and is responsible for validating test data works in Carrier’s preproduction Agent portal.
Tech: Responsible for validating the test data works in the API.
5. Pre-prod Carrier Agent Portal - User Credentials (Username, password) and URL
Business: Responsible for obtaining the pre-production portal credentials, documenting the credential, and confirming the credentials work in the portal.
Business: Responsible for obtaining the pre-production portal credentials, documenting the credential, and confirming the credentials work in the portal.
6. Pre-prod API - URL, Credentials (Username, password, producer code national/per state, unique key/ID)
Business: responsible for obtaining the pre-production API credentials.
Tech: responsible for verifying API credentials work and a request can be made to the API.
Business: responsible for obtaining the pre-production API credentials.
Tech: responsible for verifying API credentials work and a request can be made to the API.
7. Carrier coverage mapping complete for line of business
Business: Responsible for delivering coverage limit mapping.
Tech: Responsible for validating information in mapped and meets dev needs.
Business: Responsible for delivering coverage limit mapping.
Tech: Responsible for validating information in mapped and meets dev needs.
8. Development Stories Created
Production Management: Responsible for creating stories and reviewing with tech team
Production Management: Responsible for creating stories and reviewing with tech team
9. Dev Intro meeting (Carrier technical/busi tech folks introduced to our Product Owner & Architect)
Business: Responsible for scheduling meeting with carrier’s tech team and internal tech team.
Business: Responsible for scheduling meeting with carrier’s tech team and internal tech team.
10. Detail Design
Detail design presented to the team, hours assigned and marked Sprint-Ready
Detail design presented to the team, hours assigned and marked Sprint-Ready
11. Request carrier user access to testing/pre-prod version (provide carrier contact name/email to dev/Product Owner)
Business: Responsible for providing a list of carrier users (name and email) who need access to Stage.
Business: Responsible for providing a list of carrier users (name and email) who need access to Stage.
12. Attended Testing
Tech: Responsible for providing the carrier’s users with access to the stage environment and resolving all issues the carrier has identified that need to be fixed before go live.
Carrier: Responsible for the validation they feel is needed.
Tech: Responsible for providing the carrier’s users with access to the stage environment and resolving all issues the carrier has identified that need to be fixed before go live.
Carrier: Responsible for the validation they feel is needed.
13. Production Carrier Agent Portal - URL and User Credentials (Username, password)
Business: Responsible for obtaining the production portal credentials, documenting the credential, and confirming the credentials work in the portal.
Business: Responsible for obtaining the production portal credentials, documenting the credential, and confirming the credentials work in the portal.
14. Production API - URL, Credentials (Username, password, producer code national/state, unique key)
Business: responsible for obtaining the production API credentials, documenting the credentials
Tech: responsible for verifying API credentials work and a request can be made.
Business: responsible for obtaining the production API credentials, documenting the credentials
Tech: responsible for verifying API credentials work and a request can be made.
15. IVANS Downloads Enabled
Business: Confirm with agency management that IVANS activation has been completed by carrier.
Business: Confirm with agency management that IVANS activation has been completed by carrier.
16. Provide list of agents names and emails for user login creation to the carrier
Business: responsible for getting agents access to production and onboarded.
Business: responsible for getting agents access to production and onboarded.
It's just as simple as getting carriers to open up their APIs....#insurtech
• • •
Missing some Tweet in this thread? You can try to
force a refresh
