Skip to main content
Marketplace users can use platform storage when enabled, supply cloud storage credentials, or reuse previously saved credentials. Signed-link expiration and object retention are separate: the API generally requests a 24-hour link, but the configured bucket lifecycle controls retention. A supplied Azure SAS keeps its own expiry.

Supported Marketplaces

Tornado API is available on multiple API marketplaces, allowing you to use the service without managing your own API keys.

RapidAPI

The world’s largest API marketplace

Apify

Web scraping and automation platform

Zyla API Hub

Premium API marketplace

Key Differences from Direct API

Marketplace features and limits depend on the integration configuration. Direct accounts can offer additional capabilities, subject to their own plan and key limits. Consult your response notices and the dashboard rather than assuming direct access is unlimited.

RapidAPI

Authentication

Use the host and request URL from your active RapidAPI listing. Send your subscription key to that gateway; it supplies the proxy secret and tenant identity required by Tornado. The subscription key alone is not direct Tornado authentication:

Subscription Tiers

Use the plans and limits shown on the active marketplace listing. A marketplace subscription tier does not by itself remove Tornado feature or admission limits.

Apify

Use Run mode in the Actor console or its run API. The current Actor implementation rejects Standby HTTP mode and requires completion tracking; wait_for_completion=false is not supported. Example Actor input:
Read results from the run’s dataset. Storage is optional and can be supplied in the Actor input. Use the input schema and pricing of the Actor version you run; do not use an old /jobs Standby example as the Actor run API contract.

Zyla API Hub

Authentication

Use the request host/path and credentials supplied by the Zyla integration (replace the example host below). Adding zyla_ to an arbitrary token does not grant access:

Storage Configuration

Storage credentials can be omitted when saved credentials or platform storage are available. Platform fallback is controlled by MARKETPLACE_DEFAULT_STORAGE (enabled by default); if disabled, the request needs customer storage. Supplied credentials are validated and persistence is attempted for the marketplace identity, but a successful job admission does not guarantee that persistence succeeded. Your cloud account controls retention; temporary platform links should be consumed promptly.

Supported Providers

Or with SAS Token:

Security

Your storage credentials are:
  • Secret data - Credentials should be sent only through the documented credential fields; do not put them in workflow logs or public examples.
  • Saved for reuse when persistence succeeds - The service attempts to save settings for the authenticated marketplace identity using its configured secure storage.
  • Validated - Supplied credentials pass shape/backend checks and a storage probe, or reuse a cached successful probe for up to five minutes. A write/delete probe alone does not prove that a supplied SAS allows a later read.

Error Handling

Common errors for marketplace users: