Skip to main content
A user with the Configuration Manager role must create these credentials in SAP Fieldglass before the connection can be made.

Find your API credentials

This method uses the SAML assertion grant. A SAML assertion generated for a valid SAP Fieldglass
user is sent alongside the client ID and client secret, scoped to a company code.

1

Create the API application key

Sign in to SAP Fieldglass with the Configuration Manager role, then follow
Create API Application Key or Web Service
in SAP’s REST API integration guide.

  • Client ID: a valid SAP Fieldglass username. This user’s permissions govern what the integration can access.
  • Client Secret: that user’s application password, or a license key generated in SAP Fieldglass. A license key avoids issues with password rotation.
  • Application Key: the X-ApplicationKey value. It is optional for Connector, Identity (SCIM), and Reporting APIs.
2

Generate the SAML assertion

Generate a SAML assertion for a valid SAP Fieldglass user in your identity provider, then copy the base64-encoded
SAML Assertion across. It is sent as the Assertion parameter of the token request.

  • A SAML assertion is short-lived, so update the stored value whenever your identity provider issues a new one.
3

Find your company code and environment URL

Company Code is your SAP Fieldglass company code, which is sent as the scope of the
token request. The Environment URL is the hostname of your SAP Fieldglass environment,
without the protocol and without a trailing slash.

  • Format: <company>.fgvms.com
  • Example: www.fieldglass.net
  • Access tokens have limited lifetimes (the current default is 7200 seconds = 120 minutes).
1

Connect

  • Click Connect.
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup.
2

Use Actions

Connect an AI platform to the linked account’s actions. See AI Platforms.Other ways to call actions are listed in Protocols & SDKs.