How to contact APITube support#

The two fastest ways to reach APITube support are the live chat widget on any Help Center page and email at [email protected]. The chat opens a conversation where you can send the team a message; the email address is the general contact for your account and anything not covered elsewhere. Product feedback has its own address — send bug reports and feature requests to [email protected] — and platform-wide problems are tracked on the status page at status.apitube.io.

Which channel to use depends on what you need: a quick question, a billing or key problem, a bug, a feature idea, or a check on whether the API itself is down. This article maps each situation to the right channel so your message reaches the correct place the first time.

What are the ways to contact APITube support?#

APITube gives you several channels, and picking the matching one gets you a faster answer:

• Live chat — every Help Center page shows a chat widget in the corner. Open it to send the team a message directly from the page you are reading, without switching to email.
• Email [email protected] — the general support address for account questions, billing, API keys, and anything not covered by a more specific channel. It is listed as the official Contact on the APITube About page.
• Email [email protected] — the address for product feedback: bug reports, feature requests, and requests to add a new news source.
• Contact form — the /contact page on apitube.io takes your name, email, and message and sends it to the team, which is handy when you do not want to open your mail client.
• Status page — status.apitube.io shows whether the platform is operational and lists past incidents, so you can tell a real outage from a problem on your side.

Which email should I use, support@ or hello@?#

APITube runs two contact addresses, and using the right one routes your message correctly:

• [email protected] — the general contact for your account and everything else: login trouble, billing, subscriptions, API keys, quota, and usage questions. This is the address published as the official Contact on the company’s About page and referenced as the “support service” in the documentation.
• [email protected] — product feedback: reporting a bug, requesting a new feature, or asking to add a news website. If your message is “here’s something that’s broken” or “here’s something I wish the API did,” [email protected] is the right address.

When you are unsure, [email protected] is the safe default — the team can route it internally. For adding a publication specifically, see how to request a new news source, which walks through checking coverage before you write.

How do I get help fastest?#

Two habits make support faster. First, read the HTTP error code your request returned before you write in — many “the API is broken” reports are a 401, 402, 403, or 429 on the caller’s side, each with a specific ER… identifier you can fix yourself. The full map is in understanding API error codes. Second, if calls are failing broadly, check status.apitube.io first — a live outage is reported there, and there is nothing support can add beyond the incident update. See where to check API status and uptime for how to tell an outage from a key or quota issue.

When you do write, include the concrete details: the endpoint you called, the exact error code and message, and a request example with your key redacted. That turns a back-and-forth into a single reply.

Where do I report a bug or request a feature?#

Send both to [email protected]. For a bug, describe what you called, what you expected, and what happened instead — the endpoint, parameters, and the error code make it reproducible. For a feature request, describe the outcome you need; feedback feeds into what the team prioritizes. The same address also handles requests to add a new news source, so any “please change or add this” message belongs there.

To see what has already shipped before you ask, the public changelog at docs.apitube.io/platform/changelog lists product updates — your requested feature may already be live.

Common Questions#

• What is the APITube support email?
• Is there a live chat for support?
• How do I report an API bug?
• How do I know if the problem is an outage?

What is the APITube support email?#

The general support email is [email protected] — the official Contact address for account, billing, API-key, and usage questions, listed on the APITube About page. Product feedback (bugs, feature requests, and new-source requests) goes to [email protected] instead. If you are not sure which fits, use [email protected] and the team will route it.

Is there a live chat for support?#

Yes. Every Help Center page shows a live chat widget in the corner. Opening it lets you send the APITube team a message right from the page you are on, so you do not have to switch to email for a quick question. There is no published response time, so treat the reply — by chat or email — as the confirmation.

How do I report an API bug?#

Email [email protected] with the details that make the bug reproducible: the endpoint you called, the parameters, the HTTP status and ER… error code you received, and what you expected instead. A concrete request example (with your API key redacted) is the single most useful thing to include. The same address takes feature requests and requests to add a news source.

How do I know if the problem is an outage?#

Read the error code and check the status page. A 401, 402, 403, or 429 is on your side — a key, billing, access, or rate-limit issue you can fix without contacting anyone. A 500 (ER0183) across many requests points at the platform, and that is what status.apitube.io reports. See where to check API status and uptime for the full outage-vs-your-side checklist.