Importly

FAQ

Can I import private or password-protected URLs?

Not currently. Importly only supports publicly accessible URLs. If the file is private, you must make it temporarily accessible or sign it appropriately before calling our API.

What if the download is extremely large?

We recommend checking /metadata first to see file size. If the file is excessively large, consider splitting it or ensure you have sufficient credits.

Is there a limit to how many URLs I can process concurrently?

Yes, we implement both rate limiting and concurrency controls:

Rate Limits

  • Import requests: 240 per hour, max 2 concurrent imports
  • Metadata requests: 1,000 per hour, max 5 concurrent requests
  • Status polling: 3,600 per hour (1 per second)

Concurrency Limits

  • Import jobs: Maximum 2 concurrent imports (prevents resource overload)
  • Metadata requests: Maximum 5 concurrent requests

If you exceed these limits, you'll receive a 429 Too Many Requests response with details about the specific limit exceeded and when to retry.

How does pricing work?

We offer two simple options:

  • Free plan: 1 GB of credits included to get started
  • Pay as you go: $0.003 per MB processed with no monthly commitments

Metadata requests: Fixed cost of $0.01 per successful request

All plans include access to hundreds of supported platforms, 7-day file retention, webhook notifications, and full API access.

What happens when I run out of free credits?

Once you use your 1 GB free allowance, you can set up billing to continue with pay-as-you-go pricing at $0.003 per MB, or purchase additional credits to top up your account.

Can I store imported media in my own S3 bucket?

Yes! Importly supports S3 storage integration. You can configure your AWS S3, Cloudflare R2, Backblaze B2, or any S3-compatible storage to automatically upload imported media to your own bucket. This gives you full control over your media storage, allows long-term retention beyond 7 days, and enables easy integration with your existing infrastructure. Learn more in our S3 Storage Integration Guide.

How secure is my S3 configuration?

Your S3 credentials are encrypted before being stored in our database using AES-256-GCM encryption. We only require minimal IAM permissions (PutObject) to upload files to your bucket. We recommend creating a dedicated IAM user with limited permissions and rotating keys periodically. See the S3 Storage Integration Guide for detailed security best practices.

Can I use S3 storage with different buckets?

Yes, you can configure a default bucket in your dashboard settings and override it per-request using the storageBucket parameter. This allows you to route files to different buckets based on your use case (e.g., separate buckets for production and development, or different buckets for different clients).

What happens if S3 upload fails?

If the S3 upload fails for any reason, the file will still be saved to Importly's storage as a fallback, and you'll receive the standard mediaUrl pointing to Importly's servers. The file will be available for up to 7 days on our servers.

Best Practices