TikHub pricing explained, plus an alternative

TikHub sells prepaid credits. You top up first, and each call takes credits from your balance. New accounts get about 50 free requests, one time.

• —Base rate. $1.00 per 1,000 requests, or $0.001 per request.
• —Volume discount. $0.50 per 1,000 requests, but only past 30,000 calls in a day. Below that, every call is at the base rate.
• —Credit weights. Endpoints cost different amounts of credits. Check the weight of each endpoint you plan to call.
• —Rate limit. 10 requests per second by default. More needs a higher tier.
• —Enterprise. Starts at $3,000.
• —Failed calls. TikHub does not publish whether a failed call is charged.

Example: 100,000 calls a month is about 3,300 a day. That stays under the 30,000 a day discount, so every call is at the base rate. Before credit weights, that is about $100 a month.

• —Volume math. Discounts only start past a daily volume. Below that you pay the full rate, every day.
• —Credit weights. A call costs a different number of credits depending on the endpoint. Your monthly bill is hard to guess ahead of time.
• —Raw shapes. Payloads follow the platform’s own structure. Instagram and TikTok answers look nothing alike, so you write a normalizer per platform.
• —Support. TikHub uses Discord for support. Openhandle gives you direct support from our team.
• —No line on failures. The public pages do not say whether a failed request is charged.

• —Price per request. Both lower prices at volume. TikHub prices vary by endpoint and daily volume. Openhandle uses one endpoint price with monthly volume tiers.
• —TikTok and Douyin depth. TikHub includes Douyin. Openhandle combines TikTok data into one API and continues to add more endpoints.
• —YouTube. TikHub includes YouTube today. Openhandle adds platforms based on customer demand.

• —Any amount, one rate. Add balance from $10 by card. The rate does not change with how much you add, and it never expires while you use your account. Auto top-up refills it for you.
• —One call is one price. Every endpoint costs the same. Your bill is requests times price.
• —One shape for five platforms. A profile is a profile, a post is a post, on Instagram, TikTok, X, Reddit, and YouTube. One normalizer, or none.
• —Failed requests are free. Provider errors, our errors, and rate limits are never billed. A private or not-found answer is.
• —A person answers. Get direct support from our team through Crisp and email.

1. 01Start with a Test key. Create a Test key in the dashboard. Use the synthetic identifiers in the quickstart to validate your integration without charges.
2. 02Map your calls. Match your required data to the API reference. Check endpoint coverage, parameters, and returned fields before switching. Keep unsupported operations with your current provider. The table below lists common Openhandle calls.
3. 03Update paths, parameters, and authentication. Use https://api.openhandle.dev/v1 with Authorization: Bearer followed by your key. Update each endpoint path and parameter using the API reference. Profile usernames need an @ prefix in REST paths. Use the documented identifier for each post.
4. 04Map response fields. Successful responses contain platform, resource, capturedAt, source, and data. Map shared fields and platform-specific fields using the response schemas. Keep unavailable metrics as null.
5. 05Handle pagination and errors. Pass meta.cursors.next back as cursor for list requests. Cursors from another provider cannot be reused. Handle Openhandle error codes and retry only when retryable is true. See pagination and errors.
6. 06Set a cap. Pick a monthly spending cap before you go live. We stop before it, so a bad loop cannot run up a bill.
7. 07Validate before switching. Check success, empty, private, and not-found cases with a Test key. Then move to Live and compare a small sample with your current provider before switching production traffic.