Monitor your usage
Track Veille consumption per endpoint, per key, and over time.
Analytics breaks down where your credits go. Use it to find the endpoint driving your bill, confirm a migration, or catch a client that started retrying in a loop.
Traffic by endpoint
Top endpoints
API key analytics
Filter first
Pick a period (7, 30, or 90 days, or a custom range), then narrow by endpoint or by status code family. View more analytics opens the detailed screen, where you can also filter by API key and dig into recent logs without leaving Analytics.
What to look at
| View | Answers |
|---|---|
| Top endpoints | Which calls cost the most credits? |
| API key analytics | Which environment or client is responsible? |
| Traffic over time | Is consumption stable, or did something change? |
| Status codes | Are failures wasting calls without producing results? |
When numbers look wrong
- Confirm the workspace in the sidebar switcher — balances never mix across workspaces.
- Confirm the period filter. A quiet 7-day view can hide a spike from last month.
- Compare credits usage with total requests. If requests are high but credits are not, you may be hitting free endpoints or getting a lot of errors.
Check your balance from code
The usage endpoint returns the same numbers as the dashboard and is free to call. Query it on a schedule and alert your team before the balance runs out:
curl "https://api.veille.io/v1/usage" \
-H "x-api-key: $API_KEY"Analytics is aggregated and can lag by a few minutes. For request-level accuracy, use the request logs.