Third Party API Integration Services: Connecting Twitch and FastSpring
Third party API integration services connecting Twitch and FastSpring, so a purchase in one system triggers a notification processed in the other. Delivered to spec, later expanded into ongoing work.
- Geography
- Sweden
- Year
- 2020
- Stage
- 1 to 10 employees
- Team
- 2 to 3 Shipverra engineers with a single point of contact
- Duration
- June 2020 to ongoing
- Engagement size
- Less than $10,000
The situation
Toleap, a Swedish IT consulting agency, needed third-party API integration services to connect two disconnected systems: the Twitch streaming platform and FastSpring, an e-commerce provider that runs digital storefronts. Documentation for both platforms existed, but the integration itself was expected to be convoluted to build correctly.
The niche skill set the project called for had kept it unstaffed for a while before Toleap brought Shipverra in.
What we built
Shipverra built the API integration and the purchase notification pipeline between Twitch and FastSpring. When a customer completes a purchase on FastSpring, a notification carrying the purchase details is sent to Twitch and processed there — one system's transaction event becomes a structured, actionable event in the other.
Collaboration ran over Slack, Discord, and GitHub, with a single primary point of contact on the Shipverra side so Toleap had one consistent channel for questions and status.
Outcome
The integration worked to the exact specifications supplied. The final product's documentation was precise enough that Toleap called it out specifically in their Clutch review.
On the strength of that first delivery, the collaboration expanded into Spanish and Portuguese localization projects and ongoing improvement of the web solution for a larger use case.
"They maintain really clear communication."
Engagement FAQ
What does an API integration between Twitch and FastSpring involve?
It means building a pipeline so an event in one platform, such as a purchase on FastSpring, triggers a notification with the relevant details that gets processed on the Twitch side (or vice versa). Toleap's integration works this way: a purchase generates a notification carrying the purchase details, sent to the other service for processing.
Why do some API integration projects sit unstaffed even when documentation exists?
Having documentation for two platforms doesn't guarantee a straightforward build. If the actual implementation is expected to be convoluted, and the work needs a niche skill set, teams can leave the project unstaffed until they find someone who has done that specific kind of integration before. That was the case before Toleap brought in outside help.
How do payment integration services handle purchase notifications across platforms?
The typical pattern is a notification pipeline: a purchase event in one system is captured, packaged with the relevant purchase details, and sent to the second system to be processed there. That is the shape of the integration Shipverra built between Twitch and FastSpring for Toleap.
What should you look for when hiring for a niche API integration project?
Look for a team willing to work from existing documentation without demanding a fully re-scoped spec, and a communication setup (a single point of contact, tools like Slack, Discord, and GitHub) that keeps a small integration project moving without extra overhead. Toleap's engagement ran on exactly that setup, with documentation quality precise enough to be highlighted afterward.
How much do third-party API integration services like this cost, and how long do they take?
This engagement came in under $10,000, staffed with two to three Shipverra engineers working through a single point of contact rather than a full delivery team. The initial Twitch-to-FastSpring integration shipped to the agreed spec; the ongoing relationship with Toleap, running since June 2020, reflects follow-on localization and improvement work, not the length of this first build.