Partner documents
Partner API Terms of Use
Core rules for access, usage-based billing, file processing and partner responsibility.
1. Parties and access
FastSend provides the partner with technical access to the API, portal, projects, keys, webhook notifications, file storage and usage statistics. A partner is an individual or organization that has submitted an application and received access approval.
By submitting an application, the partner confirms that the project details, intended use case and contact email are accurate. FastSend may refuse onboarding or stop access when the use case presents legal, reputational, financial or technical risks.
2. Billing and limits
Partner mode uses usage-based billing: active file storage and outbound traffic are metered separately. The free allowance, rates and credit limit are displayed in the portal and API documentation.
Partner transfers always have a finite retention period. The default production value is 365 days; a project may set a shorter period or an agreed longer period within the server-side maximum of 3,650 days. The partner may delete a transfer earlier. If the balance reaches the credit limit, API access, direct downloads and new operations may be temporarily paused until the balance is topped up.
3. Prohibited use cases
- Hosting or distributing illegal content, malware, phishing, spam, or material that infringes third-party rights.
- Using the API for pornography, illegal casinos, fraudulent schemes, circumvention of blocking measures, pirated content, or bulk messaging without recipient consent.
- Attempts to conceal the actual use case or bypass billing, limits, traffic accounting, download protection or technical service restrictions.
4. Keys, staff and security
The machine API key is a secret of the partner backend. It must not be entered into the browser portal or placed in public JavaScript, mobile applications without a protected backend, repositories, logs or messages. Staff use separate portal credentials with restricted roles; those credentials do not replace production API keys.
The partner is responsible for staff actions, correct webhook URL configuration, protection of its backend and timely revocation of compromised keys.
An upload-resume key, recipient-specific link, webhook secret and signed download link are different scoped secrets. They must not be substituted for one another, stored in public logs, or exposed to client-side code beyond what the use case requires.
5. Files, direct downloads and data
A partner may create direct file-download links without an intermediate FastSend page. These links are signed, expire, account for actual outbound traffic and remain subject to the general balance, download-limit and file-deletion logic.
Downloads of individual files, archives and resumed downloads may be counted separately to enforce access limits and bill outbound traffic correctly. When a technical error is confirmed, FastSend may make an internal adjustment while retaining an audit-log entry.
The partner decides who receives links and which files are uploaded. FastSend is not the editor or owner of partner content, but may delete files and suspend access when the terms or applicable law are violated.
6. Responsibility and support
FastSend works to keep the platform operational but does not guarantee uninterrupted availability, permanent file availability or the absence of maintenance. The partner must keep its own backups of critical data.