We're announcing today that APITube has acquired GetNewsAPI. The two products are joining forces under a single brand: APITube. Existing GetNewsAPI customers will be migrated, the getnewsapi.com domain will redirect to apitube.io, and from this point forward all news API development happens here.
This is a full merger of brands and infrastructure, not a side investment. We want to be upfront about that — and explain why.
Why we made this move
The news API space has been fragmented for years. Multiple smaller providers chasing similar source lists, building parallel scraping pipelines, duplicating engineering work that should be commoditized. For the developers and data teams on the buying side, that fragmentation translates into real cost: evaluating overlapping vendors, splitting traffic across providers, reconciling inconsistent schemas.
Acquiring GetNewsAPI lets us collapse two of those overlapping efforts into one. Concretely:
- Source coverage consolidates. GetNewsAPI's source list folds into APITube's existing 500,000+ verified sources. Where coverage overlapped, we keep the better implementation; where it didn't, the combined catalog gets broader.
- Engineering effort consolidates. One team is now responsible for crawl reliability, schema, sentiment analysis, entity recognition, and multilingual coverage — instead of two teams solving the same problems separately.
- Roadmap focus sharpens. The energy that previously went into running two products goes into the things that actually move the needle for customers — data quality, latency, language and country coverage, and AI-driven enrichment.
This isn't a financial story we're going to tell here — terms aren't being disclosed. The story we care about is the operational one: fewer duplicated efforts, more focused investment in the platform.
What changes for GetNewsAPI customers
If you're using GetNewsAPI today, nothing breaks immediately. Your endpoints continue to work during the migration window. We're publishing a separate, detailed migration guide that covers:
- API key transfer to APITube without re-registration
- Endpoint mapping between the two APIs
- Schema differences and how to handle them
- Plan continuity — your existing tier and pricing carry over
The getnewsapi.com domain will redirect to apitube.io. Your existing commitments — paid plan, rate limits, billing cycle — are honored. If you have questions before the migration guide lands, our support team is ready to walk through your specific setup.
What changes for current APITube customers
For now, nothing on your side. No endpoint changes, no schema changes, no pricing changes.
What you'll notice over the next quarters is the indirect effect: the engineering capacity that previously ran two parallel products is now pointed at one. That means faster iteration on the things customers ask for most — additional language and country coverage, deeper entity and industry tagging, better historical data access, and continued investment in the News API.
What's next
We'll publish the GetNewsAPI migration guide as a follow-up post. If you're a GetNewsAPI customer and want to migrate early, reach out to support and we'll help you over.
If you're new to APITube and want to see what the consolidated platform looks like, the pricing page and the documentation are the right places to start. There's a 14-day trial — no commitment beyond that — to evaluate the API on your own data before deciding.
Thanks to the GetNewsAPI team for the work that got their product to where it is, and to our customers for the trust that made this possible. More to come.
创建帐户 Google 
创建帐户 GitHub 