Skip to content
KiweelyKiweelyKiweely

Auditing External API Calls in Workday Sign-On History and Activity Logs

Trace external Workday OAuth sign-ins and API requests using four native tools: Signons and Attempted Signons for auth events, View User Activity for 30-day read/write/download calls, View API Clients for client inventory, and View User or Task or Object Audit Trail for mutations.

  • Checked against Workday on
  • Applies to Workday Security & Auditing
  • 5 min read
  • Published
  • By Kiweely
On this page

Workday does not bundle OAuth sign-ins, read-only API queries, and data-modifying transactions into a single log screen. To audit external OAuth 2.0 applications end-to-end, correlate four native Workday reports: View API Clients (client & scope inventory), Signons and Attempted Signons (authentication & token handshakes), View User Activity (read, write, and RaaS download calls over the last 30 days), and View User or Task or Object Audit Trail (permanent business process and object mutations).

Which Workday Report Answers Which Audit Question?

Security and compliance teams investigating an external application or SIEM feed should match each investigative question to the exact Workday report and securing domain:

Audit Question Workday Report / Task Securing Domain (System FA) Retention & Row Limits
Audit QuestionWhich OAuth clients exist, what scopes do they hold, and who owns refresh grants? Workday Report / TaskView API Clients (API Clients & API Clients for Integrations tabs) Securing Domain ( System FA)Security Administration Retention & Row LimitsLive configuration inventory
Audit QuestionWhich worker authenticated via SSO/OAuth, from what IP, and did any sign-ins or token exchanges fail? Workday Report / TaskSignons and Attempted Signons (plus Candidate Signons and Attempted Signons for external career sites) Securing Domain ( System FA)System Auditing / Security Administration Retention & Row LimitsQuery by date/time window and account
Audit QuestionWhich REST reads, WQL queries, tasks, or RaaS reports did an account read or download? Workday Report / TaskView User Activity (or /activityLogging REST API / User Activity data source) Securing Domain ( System FA)System Auditing (requires Enable User Activity Logging on Edit Tenant Setup - System) Retention & Row Limits30 days max; 50,000 rows interactive (250,000 rows background / REST API); ~2-minute write lag
Audit QuestionWhat exact field values changed on a worker, position, or business process, and who submitted it? Workday Report / TaskView User or Task or Object Audit Trail, View Audit Trail, View Worker History Securing Domain ( System FA)System Auditing (Worker Data: Historical Staffing Information for Worker History) Retention & Row LimitsPermanent transactional audit history

Step 1: Audit Client Inventory and Active Grants in View API Clients

Start every review by checking which external clients can mint OAuth credentials at all:

  1. Run the View API Clients report.
  2. Inspect the API Clients tab for user-delegated clients (registered via Register API Client):
    • Review Client Grant Type, Access Token Type, Redirection URI, Refresh Token Timeout (in days), and Scope (Functional Areas).
    • Open related actions (API Client > Manage Refresh Tokens) to inspect active user-delegated refresh grants or revoke suspicious sessions.
    • Open related actions (Auditing > View Audit Trail) on the API client object itself to see who created the client, when scopes were modified, or when a Client Secret was regenerated.
  3. Inspect the API Clients for Integrations tab to audit headless ISU clients, checking specifically which clients have Non-Expiring Refresh Tokens enabled and which Integration System User each client binds to.

Step 2: Trace Authentication Events in Signons and Attempted Signons

Whenever a worker signs in on Workday’s Authorization Endpoint (/<tenant>/authorize) or an API client exchanges credentials, Workday evaluates your authentication policies and logs the sign-on event.

  1. Run Signons and Attempted Signons for a tight time window (keep date/time ranges narrow on large production tenants for fast execution).
  2. Inspect key columns:
    • Workday Account: Confirms the exact worker account (or ISU) that authenticated.
    • Authentication Type: Distinguishes SAML, OAuth 2.0, User Name Password, or MFA challenges.
    • Session IP Address: Shows the browser IP for interactive SSO sign-ins or the caller’s outbound NAT IP for API token handshakes (cross-check against your Maintain IP Ranges allowlist).
    • Failed Signon / Failure Message: Pinpoints expired SAML assertions, invalid certificate keyInfo signatures, locked accounts, or disallowed IP ranges.

Step 3: Monitor API Reads, Writes, and RaaS Downloads in View User Activity

Transactional audit trails (View Audit Trail) record changes to Workday objects, not read-only views. To audit reads—such as an external app querying GET /workers, running a WQL query, or downloading a custom RaaS report—enable and query User Activity Logging.

Enabling User Activity Logging

  1. Run Edit Tenant Setup - System (requires Modify on Set Up: System in the System functional area).
  2. Under User Activity Logging, select the Enable User Activity Logging check box (ensure alignment with your organization’s privacy/GDPR notice).
  3. Click OK.

Reading the View User Activity Columns

Run View User Activity (or build a targeted custom report on the User Activity data source) and filter by System Account or time range:

View User Activity Field What It Shows for External OAuth Calls
View User Activity FieldRequest Time What It Shows for External OAuth CallsTimestamp of the API or UI call converted to the report runner’s time zone
View User Activity FieldSystem Account What It Shows for External OAuth CallsThe authenticated Workday Account (the individual employee for user-delegated OAuth; for proxy sessions in Sandbox, shows both proxying and target accounts)
View User Activity FieldIP Address What It Shows for External OAuth CallsSource IP address associated with the caller’s session/request
View User Activity FieldUser Agent What It Shows for External OAuth CallsClient HTTP User-Agent header or browser/OS signature
View User Activity FieldTask What It Shows for External OAuth CallsThe Workday task, REST resource operation, or custom report accessed
View User Activity FieldTarget What It Shows for External OAuth CallsThe specific business object instance (e.g., worker or time-off event) acted upon
View User Activity FieldActivity Category What It Shows for External OAuth CallsREAD (GET/query with no mutation), WRITE (POST/PUT/PATCH task mutation), DOWNLOAD (report export/background run), or OTHER

Exporting to Your SIEM Before the 30-Day Purge

Because Workday purges user activity older than 30 days during weekly maintenance and caps interactive report runs at 50,000 rows, enterprise security teams export logs programmatically on a schedule (at least weekly, typically hourly or daily) via the User Activity Logging REST endpoint (/activityLogging, up to 250,000 rows per background run):

Works
GET /ccx/api/privacy/v1/gms/activityLogging?from=2026-11-15T00:00:00Z&to=2026-11-15T06:00:00Z&limit=1000 HTTP/1.1
Host: services1.wd3.workday-host.example
Authorization: Bearer 7c3obrknwd6nnkxv0r64jdpbx
Accept: application/json

Step 4: Audit Write Transactions in View User or Task or Object Audit Trail

Whenever an external OAuth client submits a write operation—such as Request Time Off or updating contact details—verify permanent non-repudiation in Workday’s core audit trail:

  1. Open the target worker or event and select Related Actions > Auditing > View Audit Trail (or run View User or Task or Object Audit Trail filtered by the worker’s Workday Account and date range).
  2. Confirm that Submitted By / Person records the employee’s own Workday Account, timestamp, business process step history, and before/after attribute values.

This native per-employee attribution is why Kiweely Bridge (coming next) and Kiweely Leaf (coming next) mandate user-delegated OAuth rather than shared Integration System Users—pairing Workday’s authoritative sign-on and business-process logs with Bridge’s schema-locked telemetry (recording only timestamp, tenant ID, tool name, HTTP status, and latency, with zero HR payloads written to logs).

Frequently asked questions

Why don't API calls from the last 60 seconds appear in View User Activity?

For database performance, Workday flushes user activity records approximately every 2 minutes. Wait 2 to 3 minutes before concluding an event was not logged.

How long does Workday retain events in the View User Activity report?

Workday retains up to the last 30 days of user activity events and purges older entries during the weekly maintenance window. Export activity at least weekly via custom reports or the /activityLogging REST API if your SIEM requires longer retention.

Why is View User Activity empty in our tenant?

User activity logging must be explicitly turned on: run Edit Tenant Setup - System, scroll to User Activity Logging, and check Enable User Activity Logging after reviewing internal privacy and GDPR policies.

How does user-delegated OAuth change what our auditors see compared to an ISU?

With a user-delegated client (Register API Client), System Account in View User Activity and business process history shows the actual employee who authenticated. With an ISU integration client, every employee's query collapses under one shared ISU account.

Sources checked

Related guides

All guides

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.