Developer API Keys
Generate and manage product-specific API keys for Seev developer products.
⬡ Dashboard feature
No API or code integration requiredAPI keys authenticate requests to Seev API products. In the Developer Dashboard, keys are created per product and per environment, so you can separate sandbox and production access.
Before generating keys, open the Developer Dashboard, accept the developer terms, and select the API products you want to use.
How product keys work
Each Seev API product is backed by a separate service. When you generate a key, choose the product the key belongs to:
| Product | Key scope |
|---|---|
| Checkout API | Checkout sessions and payment collection requests. |
| Exchange Widget API | Embedded exchange widget requests. |
| KYC | Verification API requests when available. |
Because products are separate services, each product has its own keys. A merchant may also create multiple keys for the same product, for example one Checkout API key for a web app and another Checkout API key for a mobile app.
Authenticate requests
Use the API key generated for the product and environment you are calling. Send it from your server when making requests to Seev.
POST /v1/checkout/sessions HTTP/1.1
Host: api.seevcash.com
Authorization: Bearer <your_api_key>
Content-Type: application/jsonKeep API keys on your server. Do not include them in browser code, mobile apps, client-side bundles, screenshots, or logs.
Generate a key
- Open Seev API -> API Keys.
- Click Generate Key.
- Select the product you want to generate the key for.
- Enter a key name that describes where it will be used.
- Optionally enable IP whitelisting.
- Click Create Key.
Good key names are specific to the app or service using them, for example:
| Example key name | Use case |
|---|---|
Tally Mobile App | Checkout requests from a mobile app backend. |
Merchant Portal | Checkout requests from an admin or merchant web app. |
Exchange Widget - Website | Exchange widget requests from a public website. |
IP whitelisting
IP whitelisting restricts where a key can be used from. When enabled, only requests from the IP addresses you provide should be accepted for that key.
Use IP whitelisting for server-side integrations where your outbound IP addresses are stable. Avoid enabling it for environments where IP addresses change frequently unless you can keep the list updated.
Environments
Keys are environment-specific:
| Environment | Purpose |
|---|---|
| Sandbox | Test integrations without live money movement. |
| Production | Process live API activity. |
When you switch the developer environment in the dashboard, the API Keys tab shows keys for the selected environment.
Store keys securely
Store API keys in environment variables or a secrets manager such as AWS Secrets Manager, HashiCorp Vault, Doppler, or your hosting provider's secret store. Load keys at runtime and keep separate keys for sandbox and production.
# .env (local development only)
SEEV_CHECKOUT_API_KEY=your_sandbox_or_production_key# .env.example (safe to commit)
SEEV_CHECKOUT_API_KEY=- Do not commit
.envfiles - Do not hard-code keys in configuration files
- Do not print keys in logs and error reports.
Authentication errors
If a request is rejected with 401 Unauthorized, check that:
- The request includes the API key.
- The key belongs to the product you are calling.
- The key belongs to the selected environment.
- The key is active and has not been revoked or disabled.
- The key value does not include extra whitespace.