Traffic Director API
analytics:googleapis-trafficdirector · cloud.google.com/traffic-director ↗
About the Traffic Director API API
Traffic Director API API on Apizie: 1 endpoint (POST /v3/discovery:client_status) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://zieapi.vercel.app/v1/analytics:googleapis-trafficdirector/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | analytics:googleapis-trafficdirector |
|---|---|
| Status | Your key |
| Endpoints | 1 |
| Category | Analytics |
| Source | cloud.google.com/traffic-director |
| Base URL | https://zieapi.vercel.app/v1/analytics:googleapis-trafficdirector/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
Traffic Director API API FAQ
How do I call the Traffic Director API API?
Create a free Apizie key, then send POST https://zieapi.vercel.app/v1/analytics:googleapis-trafficdirector/trafficdirector-discovery-client-status with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the Traffic Director API API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. Traffic Director API itself also needs your own key from googleapis.com.
Can AI agents use the Traffic Director API API?
Yes. Add the Apizie MCP server (https://zieapi.vercel.app/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key analytics:googleapis-trafficdirector.
What is the status of the Traffic Director API API?
Needs your own provider key (bring your own key)