Workday Security
Collection of Workday Security APIs for managing authentication, authorization, and security configurations including identity management, security groups, audit logging, privacy, and user activity monitoring.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Workday Security the way a machine reads it — 48 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Workday Security scores 67.0/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Workday Security
Each block below is one kind of artifact we hold for Workday Security. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Workday User Activity Logging API
REST API for retrieving user activity logs and signon data from a Workday tenant. Returns detailed JSON records of user actions including task information, timestamps, IP addres...
Workday Security Account Signons API
Retrieve and monitor Workday account signon events where the username corresponds to a valid Workday account. Provides detailed signon history including timestamps, IP addresses...
Workday Security Audit Logs API
Retrieve audit log entries that record system events, configuration changes, and administrative actions for compliance monitoring.
Workday Security Authentication Configuration API
Manage authentication policies and configurations including SSO, SAML, and multi-factor authentication settings.
Workday Security Compliance Reports API
Generate and retrieve compliance reports summarizing audit activity, policy adherence, and regulatory compliance status.
Workday Security Domain Security Policies API
Manage domain security policies that define which security groups have access to specific Workday functional domains and the permission levels granted.
Workday Security OAuth Tokens API
Obtain and manage OAuth 2.0 access tokens for authenticating REST API requests to Workday services.
Workday Security Security Audit API
Access security-specific audit records including permission changes, security group modifications, and access control events.
Workday Security Security Group Members API
Manage the membership of users and integration system users within security groups.
Workday Security Security Groups API
Create, retrieve, and manage security groups that control access to Workday domains, business processes, and securable items.
Workday Security Sessions API
Retrieve and manage active authentication sessions including signon history and session metadata.
Workday Security Unidentified Signons API
Retrieve and monitor unidentified signon attempts where the provided username does not correspond to a valid Workday account. Used for detecting potential unauthorized access at...
Workday Security User Accounts API
Manage Workday user accounts including account status, credentials, and associated security configurations.
Scroll within the panel for all 13 ·
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Workday Security Workday Audit and Compliance API
OPEN COLLECTIONWorkday Security Workday Authentication API
OPEN COLLECTIONWorkday Security Workday Identity Management API
OPEN COLLECTIONWorkday Security Groups API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Workday Security Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Workday Security Finops
FINOPSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Workday Security API Rules
SPECTRALJSON Schema 21
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccountRef
JSON SCHEMAAccountSignon
JSON SCHEMAActorRef
JSON SCHEMAAuditLogEntry
JSON SCHEMAAuthenticationPolicy
JSON SCHEMAComplianceReport
JSON SCHEMADomainSecurityPolicy
JSON SCHEMADomainSecurityPolicyRef
JSON SCHEMAError
JSON SCHEMAOAuthError
JSON SCHEMAPermissionChange
JSON SCHEMAPolicyPermission
JSON SCHEMASecurityGroup
JSON SCHEMASecurityGroupMember
JSON SCHEMASecurityGroupRef
JSON SCHEMASession
JSON SCHEMATargetRef
JSON SCHEMATokenResponse
JSON SCHEMAUnidentifiedSignon
JSON SCHEMAUserAccount
JSON SCHEMAWorkerRef
JSON SCHEMAScroll within the panel for all 21 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Workday Security Structure
JSON STRUCTURESecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Workday Security — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/workday-security · machine-readable index on apis.io