How can we help you?

Rate limits vary by plan: Starter (10 req/sec), Pro (50 req/sec), Enterprise (custom). Each plan also includes concurrent request limits: Starter (5 concurrent), Pro (20 concurrent), Enterprise (unlimited). Rate limit headers are included in every response to help you track usage.

Our globally distributed infrastructure delivers most metadata requests in under 500ms. Media retrieval times vary based on file size but are optimized through our high-bandwidth edge network. We maintain 99.9% uptime with automated failover systems.

Currently, we operate on a pull-based model where your application requests data on-demand. Webhook support for real-time notifications is on our roadmap for Enterprise customers. Contact our sales team if this is critical for your use case.

Credits are deducted based on request complexity. Light requests (metadata only) cost 1 credit, standard requests (metadata + media URLs) cost 2-3 credits, and heavy requests (full media download + processing) cost 5-10 credits. Check our pricing page for a detailed breakdown by endpoint.

Subscriptions are billed monthly on the date you initially subscribed. You can view your next billing date and payment history in the Dashboard under Billing. We send invoice receipts automatically to your account email after each successful payment.

Yes, you can change plans at any time from the Dashboard. Upgrades take effect immediately and you'll be charged the prorated difference. Downgrades take effect at the start of your next billing cycle to ensure you keep your current benefits until then.

For monthly subscriptions, unused credits expire at the end of each billing cycle. However, Enterprise plans can be configured with credit rollover. Pay-as-you-go credits purchased separately never expire and remain in your account until used.

We accept all major credit cards (Visa, Mastercard, American Express, Discover) processed securely through Stripe. Enterprise customers can arrange invoicing with NET-30 payment terms. We do not currently accept PayPal or cryptocurrency.

Yes, Pro and Enterprise plans support team collaboration. You can invite team members from the Dashboard under Team Settings. Each member can have different permission levels: Admin (full access), Developer (API keys only), or Billing (billing only).

For security best practices, we recommend rotating API keys every 90 days. Generate a new key in Dashboard → API Keys, update your application to use the new key, then delete the old key once you've verified the new one works. You can have up to 5 active keys simultaneously during rotation.

You can delete your account from Settings → Account → Delete Account. This action is permanent and will immediately cancel your subscription, delete all API keys, and remove your data within 30 days per GDPR requirements. Export any data you need before deletion.

We are fully GDPR compliant. We only process public data available through standard platform APIs. We do not store user-generated content beyond necessary caching (24 hours max). You can request data deletion or export at any time. Our full privacy policy and DPA are available in our legal documentation.

API request logs (timestamps, endpoints, response codes) are retained for 90 days for debugging and analytics purposes. Media content is cached for up to 24 hours for performance optimization, then automatically deleted. No personally identifiable information from retrieved content is stored beyond cache duration.

Our standard API only accesses publicly available data that any logged-out user can view. Private account data is not accessible through our API. For enterprise use cases requiring authorized data access, please contact our sales team to discuss custom solutions.

Yes, our API can retrieve Stories media and metadata, but only while the Story is publicly available (24-hour window). Stories from private accounts are not accessible. We recommend implementing real-time monitoring if you need to capture Stories before they expire.

Yes, the YouTube Media API fully supports both standard long-form videos and YouTube Shorts. Shorts are treated identically to regular videos in terms of pricing and data structure, providing the same rich metadata and stream URLs.

401 errors indicate authentication issues. Common causes: (1) Missing or invalid API key, (2) API key sent in wrong header (use X-API-Key), (3) Deleted or expired API key, (4) IP whitelist restrictions (Enterprise only). Verify your API key in the Dashboard and ensure it's correctly included in request headers.

429 errors indicate you've exceeded your plan's rate limits. This can be requests per second or concurrent request limits. Check the X-RateLimit-Remaining header in responses to monitor usage. Solutions: (1) Implement exponential backoff and retry logic, (2) Reduce request frequency, (3) Upgrade to a higher plan with increased limits.

404 errors can occur if: (1) The content was deleted or made private on the source platform, (2) The URL format is incorrect (use our validation docs), (3) The platform changed their URL structure. Ensure you're using the latest API version and check our status page for any known platform-related issues.