Begin with the player journey
An integration decision starts with how people use your platform. Decide where match discovery, team selection and leaderboard viewing belong. Review how a user moves from your existing account into the fantasy experience.
When an API fits
An API integration gives your team a route to build its own interface around the provider’s capabilities. It requires clarity about authentication, identifiers, data fields, error handling and settlement events. Ask for current documentation and test the complete journey before launch.
When H5 fits
An embedded H5 experience can place an existing player interface inside your app or website. Discuss session hand-off, navigation, screen sizes and account mapping with the integration team. Embedding a page is only one part of a reliable player journey.
Confirm the operating details
Agree the supported competitions, formats, scoring rules, account flow and settlement responsibilities. Ask how postponed, abandoned or rescheduled matches are represented. These details matter to both support teams and players.
Move from test to launch
Use the Wynso Fantasy Cricket test experience to explore the product, then contact the team for technical documentation and onboarding. Confirm the market, commercial terms and production configuration before going live.