Documentation Index
Fetch the complete documentation index at: https://docs.fluveo.com/llms.txt
Use this file to discover all available pages before exploring further.
API key types
Every account has four API keys, two for each environment:| Key prefix | Type | Environment | Use case |
|---|---|---|---|
sk_live_ | Secret | Live | Server-side API calls in production |
pk_live_ | Publishable | Live | Client-side tokenization in production |
sk_test_ | Secret | Test | Server-side API calls in test mode |
pk_test_ | Publishable | Test | Client-side tokenization in test mode |
Secret keys
Secret keys (sk_live_*, sk_test_*) can perform any API operation: creating charges, issuing refunds, reading customer data, and more. They must never be exposed in client-side code, version control, or logs.
Publishable keys
Publishable keys (pk_live_*, pk_test_*) are safe to include in client-side code. They can only be used for a limited set of operations such as tokenizing payment methods. They cannot read or modify any existing resources.
HTTP Basic Auth
All API requests authenticate using HTTP Basic Auth. Set the username to your secret key and leave the password empty.401 response:
Test mode vs live mode
Test and live environments are fully isolated at the database level. Data created with a test key is never visible to a live key, and vice versa.- Test mode (
sk_test_*,pk_test_*): Use this for development and integration testing. No real money moves. Test card numbers likepm_card_visaare available. - Live mode (
sk_live_*,pk_live_*): Use this in production. Real payment methods are charged.
livemode boolean field so you can always verify which environment a resource belongs to.
Key rotation
You can roll your secret keys from the dashboard under Settings > API Keys > Roll Key. When you roll a key:- A new key is generated immediately.
- The old key remains valid for 24 hours to allow a graceful transition.
- After 24 hours, the old key is permanently revoked.
Next steps
- Follow the Quickstart to make your first API call
- Learn about Error Handling for dealing with auth failures