Integration & Platform FAQs
Frequently asked questions about technical integration, platform options, support, and data access for WeatherIt partners.
How do we integrate WeatherIt into our systems?
Partners can offer WeatherIt via two main integration models:
flowchart TB A[Integration<br/>Options] --> B[Post-Booking Tool] A --> C[API Integration] B --> D["No development required<br/>Hosted by WeatherIt"] C --> E["Embedded in booking flow<br/>Full control"] style A fill:#e1f5ff style B fill:#e8f5e9 style C fill:#fff4e1 style D fill:#e8f5e9 style E fill:#fff4e1
Comparison
| Feature | Post-Booking Tool | API Integration |
|---|---|---|
| Development required | None | Yes |
| Integration time | Fast | Longer |
| Customer experience | Separate page | Embedded in flow |
| Control level | Standard | Full customisation |
| Best for | Quick launch, testing | Full integration |
Migration Path
Many partners start with the Post-Booking Tool and migrate to API integration later. WeatherIt supports this transition.
What technical support does WeatherIt provide?
WeatherIt provides comprehensive technical support throughout your partnership:
flowchart LR subgraph Support["Technical Support"] direction TB A["Integration Support<br/>During Onboarding"] B["Sandbox &<br/>Testing Environments"] C["Technical<br/>Documentation"] D["Ongoing Production<br/>Support"] end style A fill:#e8f5e9 style B fill:#e8f5e9 style C fill:#e8f5e9 style D fill:#e8f5e9
| Support Type | What's Included |
|---|---|
| Onboarding | Dedicated integration support, technical discovery |
| Testing | Sandbox environments, test configurations |
| Documentation | Full API docs, integration guides |
| Production | Ongoing support, incident coordination |
Technical Documentation
Detailed technical documentation is available in the Technical Integration Guide. This covers API endpoints, authentication, webhooks, and more.
Is there a sandbox or testing environment?
Yes. Before going live, partners receive access to:
- Sandbox environments for development and testing
- Test product configurations
- Simulated trigger scenarios
Testing Best Practices
| Phase | Activities |
|---|---|
| Development | Build integration against sandbox |
| Testing | Validate booking flows and data mapping |
| Verification | Ensure customer messaging aligns with outcomes |
| Go-live | Only after WeatherIt confirms readiness |
How do partners access performance and sales data?
Depending on your integration model, you may have access to:
flowchart LR subgraph Data["Available Data"] direction TB A["Transaction<br/>Reporting"] B["Policy<br/>Volumes"] C["Trigger &<br/>Payout Statistics"] D["Operational<br/>Metrics"] end style A fill:#e1f5ff style B fill:#e1f5ff style C fill:#e1f5ff style D fill:#e1f5ff
| Data Type | Access Method |
|---|---|
| Transaction reports | Dashboard or exports |
| Policy details | API or dashboard |
| Performance metrics | Periodic reviews |
| Trigger data | As relevant to operations |
Access Configuration
Access methods and reporting formats are agreed during onboarding based on your needs and integration model.
What happens if our booking system changes?
If you're planning changes to your booking system, sales channels, or customer communication methods:
- Notify WeatherIt early — Before implementation if possible
- Joint assessment — We'll assess any impacts together
- Coordinate changes — Ensure alignment before go-live
- Validate — Test that everything works as expected
Early Notification Required
Changes to booking systems can affect trigger configurations and coverage windows. Always notify WeatherIt before implementing system changes.
Integration support is available throughout your partnership. Don't hesitate to reach out with technical questions.
Updated 8 months ago
