Management Guide

Dashboard guide for personal users and small teams

This dashboard management guide covers the operational side of US Video API for freelancers, creators, founders, and small teams: adding balance, managing API keys, reviewing jobs and transactions, and using shared access when more than one person needs the account.

Who This Is For

Use this path if you are a freelancer, creator, solo developer, founder, or a small team running one shared wallet. If your team needs multiple roles, member access, or clearer billing ownership, this page still applies, but you should also read the enterprise guide.

Related docs: Use the API documentation for endpoint integration and the enterprise guide if your workflow needs role-based access and clearer internal control.

Dashboard Overview

Overview

Shows current balance, recent jobs, and your main API key path.

Credits

Top up prepaid balance and review transaction history.

API Keys

Create, rotate, rename, or delete keys used by your applications.

Shared Access

Invite a teammate into the same account without sharing login credentials.

Balance & Billing

US Video API uses prepaid balance for self-serve accounts. The normal flow is simple:

  1. Open the Credits panel.
  2. Select a deposit amount.
  3. Complete Stripe checkout.
  4. Return to the dashboard and confirm the updated balance.
Important: The wallet is account-level. If you invite teammates into a shared account, they see and spend from the same balance unless their role blocks billing actions.

API Keys

Keys are created from the dashboard and used as Bearer tokens for the API. Keep production keys out of client-side code and rotate them when team membership changes.

TaskHow To Handle It
CreateUse API Keys and create a new key for a specific application or environment.
NameUse descriptive names like prod-web, staging-worker, or agency-client-a.
RotateCreate the replacement key first, deploy it, then delete the old one.
DeleteDelete immediately if a teammate leaves or a key leaks.

Jobs & Transactions

The dashboard separates execution from billing:

  • Recent Activity tracks video jobs and job status.
  • Transaction History tracks deposits, charges, and balance adjustments.

For a small team, this usually answers the main operational questions: who is generating, whether jobs are succeeding, and how quickly balance is being consumed.

Shared Access

Small teams often need one account with one wallet and several operators. The shared access flow is:

  1. The account owner invites a teammate by email.
  2. The teammate signs in with that invited email.
  3. After acceptance, they use the same balance, keys, jobs, and transaction view as the owner.

Current shared roles:

RolePurpose
OwnerFull account control.
Billing AdminManage deposits and billing visibility.
DeveloperRun API work and manage keys.
ViewerRead-only visibility.

Best Practice

  • Use one key per app or environment, not one key for everything.
  • Keep billing authority with one owner or billing admin.
  • Invite teammates instead of sharing passwords.
  • Delete old keys after contractor or employee offboarding.
  • Move to the enterprise guide if you want a clearer internal split between finance, engineering, and observers.

Management FAQ

How do I add funds to my US Video API dashboard?

Go to Credits, select a deposit amount, complete checkout, and confirm the updated balance when you return.

How should a small team handle API keys?

Create separate keys by app or environment, label them clearly, and rotate keys when a teammate leaves or a service changes.

Can a small team share one account?

Yes. Shared access lets an owner invite teammates so they work inside one account without sharing passwords.

API Docs Enterprise Guide Pricing Dashboard YouTube Channel Contact