API Key Authentication
All Shakesco API requests require authentication using bearer tokens, regardless of which API product you’re using.Getting Your API Key
Create account
Sign up at users.shakesco.com
Deploy appropriate account
Deploy the account type needed for your use case: - Business Auto
account - For recurring subscriptions - Personal account - For payment
links
Using Your API Key
Include your API key in theAuthorization header for all requests:
API Products & Requirements
Different API products may have different account requirements:| API Product | Required Account | Get Started |
|---|---|---|
| Auto-Payments | Business Auto account | Deploy guide |
| Payment Links | Personal account + .sns username | Get username |
| Checkout | Business Auto account | Setup guide |
Security Best Practices
Recommended:- Store API keys in environment variables
- Use different keys for development and production
- Rotate keys periodically
- Never commit keys to version control
- Use separate keys for different projects
Testing
Use the test endpoints to verify your integration without charges: Auto-Payments:/delegate_address- Get test user address/buss_delegate_address- Get test business address
- All endpoints work in test mode with Sepolia testnet
Authentication Errors
401 Unauthorized Missing or invalid API key:- Verify API key is correct
- Check
Bearerprefix is included - Ensure key matches the environment (test vs production)
- Confirm key is associated with the correct account type
- Verify account type matches API product (e.g., Business Auto for subscriptions)
- Check account is fully deployed and funded
- Ensure .sns username is registered (for payment links)