We answer every email that lands in the contact form above. The quality of your reply mostly depends on two things: picking the right inquiry type in the dropdown, and giving us enough detail to reproduce what you're seeing without a second round trip. This page walks you through both — which inquiry type matches which situation, what to include, and when to expect a reply at each plan level.
The dropdown at the top of the form routes your message to the right inbox. Pick the option that matches your situation — that alone shaves hours off the response time on busy days.
Pick Technical issue in the dropdown
A 4xx/5xx you weren't expecting, an endpoint returning empty results, rate-limit confusion, webhook payloads that don't match the docs, or anything else that looks like it might be a bug on our side.
Include in your message:
Your request_id (every API response includes one), the endpoint you called, the params you sent, the status code you got back, and roughly when it happened (timezone matters for log lookup).
Pick Existing API or feature in the dropdown
The docs at /api-sources cover endpoints, params, and example responses, but if you're stuck on edge cases (pagination cursors, country-locked content, how a specific filter combines with another), drop us a note.
Include in your message:
A link to the /api-sources/<slug> page you're working from, a curl or fetch snippet showing what you've tried, and the result you expected vs. the result you got.
Pick New API or feature in the dropdown
If you'd use a dataset we don't expose yet — a new endpoint, a new social platform, a richer schema on an existing one — tell us. Most of our roadmap comes from customer asks, and we ship new endpoints monthly.
Include in your message:
What you want to do (the business problem, not just the field list), what volume you expect, and any upstream source you've already evaluated.
Pick Premium plans or pricing in the dropdown
Need a custom rate limit, a higher monthly credit allowance than the public Mega tier, lifetime credits for a one-off project, a private SLA, on-prem options, an agency reseller arrangement, or affiliate partnership.
Include in your message:
Expected monthly API volume, the endpoints you'll use most, your geography (for invoicing/VAT), and whether you need a signed MSA or DPA up front.
Pick Other in the dropdown
Building an n8n/Make/Zapier template, writing a tutorial that features SocialAPIs, podcast interviews, or a piece of research that needs sample data — we usually say yes and can grant complimentary credits for the duration of the project.
Include in your message:
Where the work will be published, your timeline, and what you'd want from us (free credits, a quote for the article, technical review of the post).
We don't run 24/7 phone support — every customer-facing reply goes through email so we can attach request logs and link to docs. Here's what you can expect on each plan, measured from when your email lands to when you get a substantive reply (not a canned acknowledgement).
| Plan | First substantive reply | Notes |
|---|---|---|
| Free tier | Within 48 hours, business days | Best-effort. We read every message but prioritise paying and trial-converting accounts first. |
| Pro / Ultra / Mega | Within 24 hours, business days | Faster turnaround. Tag your message with your account email (or sign in before sending) so we can pull your usage history. |
| Custom / Enterprise plans | Within 4 hours, business hours CET | Plus a shared Slack or Telegram channel if your contract includes one. Out-of-hours pages route to the on-call engineer. |
| Outages / incidents | As fast as we can — typically <1h | If the API is returning 5xx errors broadly, you'll usually see us comment on the status page before you can finish typing the support email. We post incident updates there in real time. |
Three places where the answer to your question may already be sitting:
Every endpoint has a README, an input schema, and a worked example with curl + JavaScript + Python + PHP + Java + Go. Pagination cursors, available filters, and rate-limit behaviour are all covered there.
Common questions about billing, the credit model (base / bonus / lifetime buckets), subscription cancellations, and data freshness are answered there in plain English.
If your question is "which plan should I be on?", the pricing page compares credit allowances, per-minute rate limits, and feature access side by side.
Free-tier emails get a reply within 48 business hours, paid plans (Pro, Ultra, Mega) within 24 business hours, and custom/enterprise contracts within 4 hours during CET business hours with a shared Slack or Telegram channel. Live incidents are usually replied to in under an hour regardless of plan.
Not for free or self-serve paid plans — every customer-facing reply goes through email so we can attach request logs, link to docs, and keep an audit trail. Custom and enterprise contracts get a dedicated chat channel (Slack or Telegram) and a scheduled video call cadence. For a one-off integration call, ask in your first support email and we'll book a 30-minute video session if it'll unblock you.
The request_id from the response (every API response returns one in the body and the x-request-id header), the full endpoint path including query params, the HTTP status code you got, the time of the call in your timezone, and a curl command we can re-run against your account. That lets us pull the matching row from our request log within a couple of minutes instead of asking three rounds of clarifying questions first.
Yes. Pick 'Premium plans or pricing' as the inquiry type and include your expected monthly call volume, the endpoints you'll use most, and whether you need recurring monthly billing, an annual prepay, or one-time lifetime credits. We typically reply with a draft quote within one business day; once you accept, the custom plan is provisioned in Stripe and your account is upgraded the same day. Lifetime credits never expire on plan changes.
Yes — public status updates and incident timelines are posted there in real time. If you suspect an outage, check the status page before opening a support ticket: most incidents already have an acknowledged update and an ETA by the time the average customer notices. Subscribe to status-page email or RSS alerts if you want to be paged automatically when we announce or resolve an incident.
Yes. Support emails go to a private inbox readable only by the on-call engineer and the founders; we don't index them for marketing and we don't share excerpts with third parties. We treat shared request_ids, account emails, and any sample payloads as confidential. If you need a formal NDA before sending sensitive details, ask for it in the first email and we'll send one over.
Scroll back to the form at the top of the page, pick the inquiry type that matches your situation, and include the details listed in the relevant card above. We'll get back to you within the window for your plan.
Prefer email? [email protected] — same inbox, same response times.