Request logs and end-user tags
Tag each call with your own id for the person it is for. Then see, filter and export calls per user.
The X-End-User header
Send X-End-User on any call. Use an opaque id from your own system, such as a hashed user id. It is optional and free.
cURL
curl https://api.vedicapi.co/v1/chart/planets \
-H "Authorization: Bearer $VEDICAPI_KEY" \
-H "X-End-User: user_8f2c" \
-H "Content-Type: application/json" \
-d '{ "datetime": "1990-10-21T00:45", "lat": 28.6139, "lon": 77.209, "tz": "Asia/Kolkata" }'Never send personal data. No names, phone numbers, emails or birth details in the tag: it is stored in your logs as sent. Use up to 64 characters of letters, numbers,
_ and -. A longer tag, or one with other characters, gets 400 invalid_end_user.Where tags show
- What you getSearch by tag, filter by endpoint and status, export CSV.
- What you getTop end users by calls this month.
- What you getRead logs from code with
end_user,endpointandsinceas filters. Free to call.
Read logs from code
cURL
curl "https://api.vedicapi.co/v1/logs?end_user=user_8f2c&since=2026-11-18T00:00:00Z&limit=100" \
-H "Authorization: Bearer $VEDICAPI_KEY"Use it to answer support questions (“what did this user see?”) or to bill your own customers per use. Each row has the request_id, time, method, endpoint, status, time in ms, units (API calls counted) and, for errors, the error message. Rows come newest first, up to 1,000 a page; pass next_cursor as cursor for the next page. Rows are kept for at least 30 days. Birth details are never stored in logs.