How to Read Your Workday Platform Consumption Console
A practical guide to the Workday Platform Consumption Console: where to find your API Activity Reports, what the numbers mean, and how to use them for optimization and renewal negotiations.
The Platform Consumption Console is where your Workday Flex Credit story becomes real. It's the difference between guessing how many API calls your integrations make and knowing exactly which integration, which API, and which IP address is driving your consumption.
If you haven't opened your PCC yet, this guide walks you through what's there and what to do with it.
Where to find it
The Platform Consumption Console is accessible to Workday administrators through the Workday admin menu. Look for "Platform Consumption Console" under the AI or administration section. If you don't see it, your security role may not include PCC access - ask your Workday security administrator to grant access through the Management Dashboard: Platform Consumption Console domain.
PCC is activated via a feature toggle in your tenant and is available in all environments after UMSA signing. There is no charge or additional SKU required to use PCC or the Agent System of Record (ASOR) - both are included at no cost.
Workday says the PCC tracks consumption for all customers, regardless of whether they've signed the Flex Credits and Platform Entitlement Policy. If you haven't signed that policy, API requests are shown for informational purposes and Flex Credits are not charged. But the data is still there, and it's still valuable. PCC is updated daily starting at 14:00 UTC, with calculations taking 1 to 3 hours depending on data volume.
What the console shows
Embedded Entitlement Overview
This is your starting point. It shows your annual API Platform Entitlement - the number of production API calls included in your subscription. It breaks down the baseline by your employee/FSE band and any SKU-based uplifts (Financials +15%, Extend +50%, etc.).
Compare this number to your actual consumption. If you're at 60% utilization with no AI agents planned, you have headroom. If you're already at 85%, you need to optimize before adding any new integrations or agents.
Rate Card
The Rate Card page is what Workday calls the "definitive consumption resource." It shows the credit rates that apply to your specific entitlement - API overage rates, agent action rates, and any other metered capabilities. The September 2026 rate card lists 60 Flex Credits per 10,000 standard API calls, but your contracted rate may differ.
Credit Entitlement
This section shows your Flex Credit balance - complimentary credits (included with your subscription), purchased credits, and remaining balance. The complimentary credits range from 15,000 to 200,000 per year depending on company size. Credits do not roll over - they reset annually.
PCC shows alerts at 80%, 90%, and 100% of credit usage. If your balance hits zero, access is not suspended - usage accrues as a negative balance until you purchase additional credits.
Agent System of Record (ASOR)
While not technically part of the PCC, ASOR is its companion governance tool. ASOR is the central hub for all agent management - it controls who can activate or deactivate agents, defines access permissions, and provides detailed data on which agents are being used, by whom, and how often. PCC relies on ASOR's Workday ID definitions to match agent telemetry to the Rate Card.
ASOR is also where you register external agents (Claude, Copilot, third-party tools) for governance and visibility. Registering external agents in ASOR is strongly recommended so you maintain oversight of which agents have access to your tenant and what actions they can perform.
API Activity Reports
This is where the operational data lives. Workday provides several report views, each retained for up to 13 months in supported regions.
Monthly API Trends. Shows your total API request volume by month. This is the first report to pull - it tells you whether your consumption is stable, growing, or seasonal. A steady upward trend means you'll hit your entitlement sooner. Seasonal spikes (open enrollment, year-end close) might push you over in specific months.
Top API Request Sources. Shows which integration systems generate the most traffic. This is the 80/20 report - a handful of integrations usually drive most of the volume. The integration system name tells you what's calling Workday, which maps directly to your integration inventory.
Top API Names. Shows which specific Workday API operations are called most frequently. A high volume of Get_Workers calls, for example, might indicate polling-heavy integrations that could be optimized with delta sync or caching.
Top IP Addresses. Shows where the API traffic originates. This helps you identify middleware platforms, cloud services, and external systems that connect to your tenant. An unfamiliar IP generating significant traffic is worth investigating.
How to use the data
Build a baseline
Export the Monthly API Trends for the last 12 months. Calculate your average monthly consumption, peak month, and annual total. Compare the annual total to your Platform Entitlement. This gives you your utilization percentage and tells you how much headroom you have.
Classify your traffic
Cross-reference the Top API Request Sources with your integration inventory. For each source, determine whether it's exempt (unmodified Core Connector), countable (custom integration), or unknown. The unknown category is the one that requires investigation - middleware platforms, partner tools, and legacy integrations that nobody remembers building.
Identify optimization targets
Sort the Top API Request Sources by volume. The top 5 sources are your optimization targets. For each one, ask: Can this integration use delta sync instead of full extraction? Can it cache reference data? Is it polling when it could be event-driven? Is it making row-by-row calls when a batch endpoint exists?
Prepare for renewal
Your PCC data is the strongest tool you have in a renewal conversation. Come with 12 months of actuals, your utilization percentage, your top consumers, and a forecast. Ask Workday specific questions about exemptions, counting rules, and entitlement sizing based on your data, not on generic policy language.
Common patterns we see
The polling multiplier. An integration that polls every minute generates 525,600 calls/year. Every 5 minutes: 105,120. Every 15 minutes: 35,040. Moving from 1-minute to 15-minute polling cuts 93% of the traffic from that integration alone.
The full-sync trap. Nightly full syncs of all employees to a downstream system generate the same volume whether 0 or 100 employees changed that day. Delta sync (only changed records) dramatically reduces volume in most environments.
The chatty middleware. iPaaS platforms that break batch payloads into individual API calls can turn a 1,000-record update into 1,000 API requests. If the middleware supports batch or composite requests, one call can replace a thousand.
The forgotten integration. Legacy integrations built during the original implementation that nobody turned off, serving a system that was decommissioned two years ago. The PCC's Top API Request Sources report surfaces these immediately.
What to do with a specific report
When you pull each report, capture the following for your records: the report date range, the raw data (export to CSV if available), the total and per-source breakdowns, and any anomalies (unexpected sources, sudden volume changes, unknown IPs). Store this alongside your integration inventory and policy documentation.
This data forms the basis of a Consumption Baseline Assessment - the starting point for any optimization or renewal strategy.
Frequently asked questions
Can I export PCC data? Workday provides the reports within the PCC interface. Whether CSV export is available depends on your tenant configuration. Some customers use RaaS or Prism Analytics to extract more detailed API telemetry.
How far back does the data go? API Activity Reports retain up to 13 months of monthly data for currently supported regions.
Who should have PCC access? At minimum: the Workday administrator, the integration lead, the finance stakeholder responsible for Workday licensing, and anyone managing AI agent deployments.
What if my PCC shows consumption I can't explain? Start with the Top IP Addresses report. Cross-reference unknown IPs against your network team's records, middleware platforms, and cloud service providers. Unexplained traffic often comes from development/test environments hitting production, middleware health checks, or partner integrations you forgot about.
Use our Flex Credits Calculator to estimate your exposure, or request a full Consumption Baseline Assessment.
Ready to Improve Your Workday?
See how Assistly® can streamline your Workday environment with 68% ticket deflection and proactive support that prevents issues before they occur.