Get Started
Best Practices
Tips for getting the most out of Synter
API Key Security
Use environment variables
Store API keys in environment variables, never in code
Rotate keys regularly
Generate new keys periodically and revoke old ones
Never commit keys to git
Add .env files to .gitignore
Don't expose in client-side code
Make API calls from your server, not the browser
Rate Limits
100
Requests per minute
10,000
Requests per day
Implement exponential backoff
When you receive a 429 status, wait and retry: 1s, 2s, 4s, 8s...
Efficient Credit Usage
Batch operations
Use list operations instead of individual gets
Cache responses
Store campaign lists locally, refresh hourly
Use free tools first
get_credit_balance and get_connection_status are free
Avoid redundant calls
Check if data changed before pulling again
Free tools (0 credits)
| Tool | Description |
|---|---|
get_credit_balance | Check your remaining credits |
get_connection_status | Verify which platforms are connected |
list_connected_accounts | See all connected ad accounts |
list_available_scripts | Browse all available automation scripts |
Was this page helpful?