One API, Three Request Tiers
The production API features stay the same across every paid plan. The commercial difference between plans is the daily request allowance attached to your account.
What You Receive
Paid access includes API credentials for the signed production endpoint plus client usage and account endpoints.
Included In Every Paid Plan
Signed Production Access
Every paid plan uses the same authenticated API flow with API key, timestamp, and HMAC signature.
Files And Folders
The backend processes TeraBox links efficiently. Folders are fetched lazily, so your client must pass `dir_path` and `page` to browse subdirectories.
Video-Ready Responses
Video items can include stream and stream-download URLs, while non-video files are handled through direct download links.
Client Usage Tools
Account, dashboard, analytics, request-history, and export endpoints are available for subscribed clients.
Production onboarding is simple
1. Test the public endpoint to confirm the response format with your links.
2. Choose the request tier that matches your daily traffic.
3. Receive your API key and API secret for signed production requests.
4. Use the account and usage endpoints to monitor activity after launch.
Important client notes
The production endpoint is `POST /v1/api` and uses request signing.
The free test endpoint is `POST /api/test` and is limited to 10 requests per day per IP.
Folder links are fetched lazily. You must pass `dir_path` and `page` in your payload to browse folders.
Common Questions
How are the plans different?
The shared API features are the same. The main difference shown publicly is the daily request allowance assigned to your account.
What does the free test show?
It runs the public test endpoint, returns a live sample response, and lets you validate how your app should parse the data before you subscribe.
What credentials do paid clients receive?
Paid clients receive an API key and an API secret. The key identifies the account, and the secret is used to sign requests to the production endpoint.
Where are the integration docs?
The public docs page now covers authentication, code samples, response fields, and client usage endpoints.
