Skip to main content

SAP Fieldglass

SAP Fieldglass is a cloud-based vendor management system (VMS) for managing contingent labor and services procurement. Its REST API lets external systems download work orders, workers, suppliers, invoices, and statements of work, and upload new or updated records back into the platform. Nexla connects to SAP Fieldglass using the OAuth 2.0 client credentials grant against your tenant's environment URL.

SAP Fieldglass icon

Power end-to-end data operations for your SAP Fieldglass API with Nexla. Our bi-directional SAP Fieldglass connector is purpose-built for SAP Fieldglass, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to SAP Fieldglass or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your SAP Fieldglass workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an SAP Fieldglass credential in Nexla, you need three pieces of information: your tenant environment URL, a client ID, and a client secret. SAP Fieldglass authenticates REST API requests using the OAuth 2.0 client credentials grant, and Nexla exchanges these values for an access token automatically against your tenant's token endpoint (/api/oauth2/v2.0/token).

To obtain your credentials, work with your SAP Fieldglass administrator to gather the following:

  1. Environment URL — This is your SAP Fieldglass tenant URL, for example https://your-company.fieldglass.net. Nexla uses it as the base URL for all API calls and to construct the OAuth token endpoint.

  2. Client ID — The client ID is a valid SAP Fieldglass username that has permission to access the REST API. Confirm with your administrator that the user account is enabled for API access.

  3. Client secret — The client secret can be either that user's application password or, to avoid problems with password rotation, a client-specific license key (application key). License keys are generated in the SAP Fieldglass Configuration Manager. Using a license key is recommended so that routine password changes do not interrupt the integration.

If SAP Fieldglass returns an error indicating that an API application or key is required, request one from your SAP Fieldglass administration team, or use the SAP Fieldglass Integration Tools to create an API application. For complete details on authentication and available endpoints, refer to the SAP Fieldglass REST API Integration General Reference Guide.

Authenticate

Credentials required

FieldRequiredSecretDescription
Client ID (Username)YesNoA valid SAP Fieldglass username used as the OAuth2 client ID for client-credentials authentication.
Client Secret (Application Password / License Key)YesYesThe application password or license key generated in SAP Fieldglass Configuration Manager for API access.
Base URLYesNoSAP Fieldglass tenant environment URL, e.g. https://your-company.fieldglass.net

Create a credential in Nexla

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter the SAP Fieldglass username in the Client ID (Username) field. This is the account used as the OAuth2 client ID for client-credentials authentication.

  4. Enter the application password or license key in the Client Secret (Application Password / License Key) field. Using a license key generated in the SAP Fieldglass Configuration Manager is recommended so that password rotation does not interrupt the integration.

  5. Enter your tenant environment URL in the Base URL field, for example https://your-company.fieldglass.net. Nexla uses this value for all API requests and to construct the OAuth 2.0 token endpoint.

    Nexla validates the credential against the SAP Fieldglass approvals endpoint using the OAuth 2.0 client credentials grant. If validation fails, confirm that the environment URL is correct and that the account is enabled for REST API access.

    For detailed information about authentication and available endpoints, see the SAP Fieldglass REST API Integration General Reference Guide.

  6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the SAP Fieldglass connector tile, then select the credential that will be used to connect to the SAP Fieldglass instance, and click Next; or, create a new SAP Fieldglass credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common SAP Fieldglass endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] Get Active Work Orders

Download active work orders, including status, dates, worker, and supplier detail.

[Rest API] Get Active Workers

Download currently active worker records.

[Rest API] Get Workers From Work Order

Download worker records associated with work orders (HR-XML/XML format).

[Rest API] Get Supplier Workers

Download workers associated with a specific supplier.

[Rest API] Get Suppliers

Download the list of suppliers configured for the buyer.

[Rest API] Get Supplier Details

Download detailed supplier record information.

[Rest API] Get Buyer Invoices

Download invoices from the buyer's perspective.

[Rest API] Get Supplier Invoices

Download invoices from the supplier's perspective.

[Rest API] Get Invoice Status

Download the current status of invoices.

[Rest API] Get Invoice Adjustments

Download invoice adjustment (credit/debit memo) records.

[Rest API] Get Statements of Work

Download statement of work (SOW) records.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

SAP Fieldglass data sources can also be manually configured to ingest data from any valid SAP Fieldglass REST API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new SAP Fieldglass data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the SAP Fieldglass destination, and select the Send to Destination option from the menu. Select the SAP Fieldglass connector from the list of available destination connectors, then select the credential that will be used to connect to SAP Fieldglass, and click Next; or, create a new SAP Fieldglass credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common SAP Fieldglass endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Worker

Upload new worker records into SAP Fieldglass.

[Rest API] Update Worker

Upload updates to existing worker records.

[Rest API] Create Work Order

Upload new work order records.

[Rest API] Update Work Order

Upload updates to existing work order records.

[Rest API] Close Work Order

Upload requests to close active work orders.

[Rest API] Create SOW Invoice

Upload invoices associated with a statement of work.

[Rest API] Create Consolidated Invoice

Upload a consolidated invoice spanning multiple work orders.

[Rest API] Update Supplier Status

Upload requests to activate or inactivate a supplier.

[Rest API] Update Statement of Work

Upload edits to an existing statement of work.

Manual configuration

SAP Fieldglass destinations can also be manually configured to send data to any valid SAP Fieldglass REST API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

SAP Fieldglass upload endpoints expect JSON in the request body. Ensure each record matches the structure required by the target upload endpoint before activating the destination.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured SAP Fieldglass endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the SAP Fieldglass endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.