SAP Fieldglass
SAP Fieldglass is a cloud-based vendor management system (VMS) that enables organizations to manage their contingent workforce, services procurement, and external talent. It provides REST APIs for managing work orders, job postings, statements of work, worker profiles, time sheets, invoices, and external talent across more than 165 countries.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles SAP Fieldglass the way a machine reads it — 53 machine-readable artifacts across 12 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 — SAP Fieldglass scores 55.5/100 (developing), 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 SAP Fieldglass
Each block below is one kind of artifact we hold for SAP Fieldglass. 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 12
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.
SAP Fieldglass REST API
Core REST API for SAP Fieldglass that allows clients to send and receive integrated data directly against the application. Supports upload (POST/PUT) and download (GET) of data ...
SAP Fieldglass Identity Management API
SCIM-based identity management API for SAP Fieldglass enabling user provisioning, deprovisioning, and lifecycle management for workers, buyers, and suppliers across the continge...
SAP Fieldglass Pick List Value Download API
Retrieves configurable pick list values from SAP Fieldglass for use in integration and data validation, including worker types, cost centers, regions, and other reference data.
SAP Fieldglass Approval API
The Approval API from SAP Fieldglass — 5 operation(s) for approval.
SAP Fieldglass Audit Trail API
The Audit Trail API from SAP Fieldglass — 1 operation(s) for audit trail.
SAP Fieldglass Get Data API
The Get Data API from SAP Fieldglass — 1 operation(s) for get data.
SAP Fieldglass Get Entities API
The Get Entities API from SAP Fieldglass — 1 operation(s) for get entities.
SAP Fieldglass Get Metadata API
The Get Metadata API from SAP Fieldglass — 1 operation(s) for get metadata.
SAP Fieldglass Get Providers API
The Get Providers API from SAP Fieldglass — 1 operation(s) for get providers.
SAP Fieldglass Order Confirmation API
The Order Confirmation API from SAP Fieldglass — 1 operation(s) for order confirmation.
SAP Fieldglass Reports API
The Reports API from SAP Fieldglass — 2 operation(s) for reports.
SAP Fieldglass Results API
The Results API from SAP Fieldglass — 1 operation(s) for results.
Scroll within the panel for all 12 ·
Pricing 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.
Sap Fieldglass 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.
Sap Fieldglass Finops
FINOPSFeatures 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Contingent Workforce Management
End-to-end management of contingent workers including job postings, work orders, time sheets, and invoicing.
Services Procurement
Manage service engagements and statements of work with suppliers and service providers.
External Talent Management
Source, engage, and manage external talent across gig workers and contractors in 165+ countries.
Vendor Management System
Track and manage supplier relationships, rates, and performance for the external workforce.
OAuth 2.0 Authentication
Secure API access using OAuth 2.0 protocol supporting web server, installed, and client-side application scenarios.
Spectral 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.
SAP Fieldglass API Rules
SPECTRALJSON Schema 15
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.
SAP Fieldglass Approval API - approvals
JSON SCHEMASAP Fieldglass Approval API - Error
JSON SCHEMASAP Fieldglass Approval API - Status
JSON SCHEMASAP Fieldglass Audit Trail API - auditTrail
JSON SCHEMASAP Fieldglass Audit Trail API - Error
JSON SCHEMAScroll within the panel for all 15 ·
Examples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security 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.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Work Order Management
Create, manage, and track work orders for contingent workers through the full engagement lifecycle.
Statement of Work Integration
Integrate services procurement statements of work with ERP and financial systems.
Workforce Analytics
Access analytics and reporting data on external workforce spend, headcount, and performance.
Identity Provisioning
Automate worker onboarding and offboarding with SCIM-based identity management.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
SAP S/4HANA
Native integration with SAP ERP for purchase orders, invoices, cost centers, and financial data.
SAP SuccessFactors
Total workforce management integration connecting internal and external talent management.
SAP Ariba
Combined services procurement workflow connecting Ariba sourcing with Fieldglass worker management.
Resources
Every other property we hold for SAP Fieldglass — 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.
Documentation 1
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 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sap-fieldglass · machine-readable index on apis.io