SignalFx Developers Guide

Developer Home

Product Docs

SignalFx

Integrations API

APIs for creating, retrieving, updating, and deleting SignalFx integrations to the systems you use.
An integration provides SignalFx with information from the external system that you're connecting to. You'll need to retrieve this information from the external system before you use the API. Each external system is different, so to see a summary of its requirements and procedures, view its request body description.

Authentication

To create, update, delete, or validate an integration, you need to authenticate your request using a session token associated with a SignalFx administrator. To retrieve an integration, your session token doesn't need to be associated with an administrator. You can also retrieve integrations using an org token.
In the web UI, session tokens are known as user access tokens, and org tokens are known as access tokens.
To learn more about authentication tokens, see the topic Authentication Tokens in the Developers Guide.

Supported service types

SignalFx offers integrations for the following:

  • Data collection from other monitoring systems such as AWS CloudWatch
  • Authentication using your existing Single Sign-On (SSO) system
  • Sending alerts using your preferred messaging, chat, or incident management service
    To use one of these integrations, you first register it with SignalFx. After that, you configure the integration to communicate between the system you're using and SignalFx.

Data collection

SignalFx integrations APIs support data collection for the following services:

  • Amazon Web Services (AWS)
  • Google Cloud Platform (GCP)
  • Microsoft Azure
  • NewRelic

Authentication using SSO

SignalFx integration APIs support SAML-based SSO integrations for the following services:

  • Microsoft Active Directory Federation Services (ADFS)
  • Bitium
  • Okta
  • OneLogin
  • PingOne

Alerts using message, chat, or incident management services

SignalFx integration APIs support alert notifications using the following services:

  • BigPanda
  • Office 365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • xMatters

NOTE: You can't create Office 365 integrations using the API, and your ability to update them in a PUT request is limited, but you can retrieve their data or delete them. To create an Office 365 integration, use the the web UI.

Viewing request body documentation

The request body format for the following operations depends on the type of integration you use:

  • POST /integration
  • PUT /integration/{id}

The response body format for the following operations also depends on the type of integration you use:

  • GET /integration
  • GET /integration/{id}


To see the request or response body format for an integration:

  1. Find the endpoint and method.
  2. For a request body, find the section REQUEST BODY SCHEMA. For a response body, find the section RESPONSE SCHEMA.
  3. Scroll down to the type property.
  4. At the end of the description for type, find the dropdown box that contains the integration type. By default, it's set to AWSCloudWatch.
  5. To see a complete list of integrations, click the down arrow. A list with a vertical scroll bar appears.
  6. Select the integration type from the list. The request body properties for this integration type now appear.

Retrieve Integrations Using Query

Retrieves integrations based on search criteria

get /integration

SignalFx API endpoint.
Replace {REALM} with the name of your realm. For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.
To find your realm, go to your profile page in the SignalFx web UI.
If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration

Retrieves one or more integration objects based on a query specified in query parameters encoded on the URL. NOTE: To ensure security, SignalFx omits some authentication and authorization properties from response objects. The integration model description for a property tells you if it's omitted from responses.

query Parameters
name
string

Integration object name to search for. You can use wildcard characters to specify the name:

  • *: Matches a run of any characters in any part of the name
  • ?: Matches any single character in any part of the name
type
string
Enum:"ADFS" "AWSCloudWatch" "Azure" "AzureAD" "Bitium" "BigPanda" "GCP" "GoogleSaml" "Office365" "Okta" "OneLogin" "Opsgenie" "PagerDuty" "PingOne" "NewRelic" "ServiceNow" "Slack" "VictorOps" "Webhook" "XMatters"

Type of integration to search for. This property is an enumerated string, and only the enumerated values are allowed.

offset
integer <int32> >= 0
Default: 0

0-relative position in the result set where SignalFx should start returning integration objects.

limit
integer <int32> >= 1
Default: 50

Number of integration objects to return from the result set

header Parameters
X-SF-TOKEN
required
string

Authentication token.

Responses

200

Successful retrieval of one or more integration objects.
NOTE: If the request is well-formed but SignalFx can't find any matching integration objects, the API still returns 200. In this case, the count property is set to 0, and the results array is empty.

Response Schema: application/json
count
integer <int64>

Number of integrations that matched the search criteria. This value is not the number of integrations returned in the response body. To learn more, see the description of results.

results
object

List of integrations, in the form of a JSON array of JSON objects. Each object contains properties that are common to all integrations as well as properties that are specific to the integration type (type property) for the object.
The size of results and the value of count are not necessarily equal:

  • If you don't specify limit or offset:
    If count > 50, then sizeOf(results) = 50; otherwise sizeOf(results) = count.
  • If you only specify limit:
    If count > limit then sizeOf(results) = limit; otherwise sizeOf(results) = count.
  • If you specify limit and offset:
    If count > (offset + limit) then sizeOf(results) = limit; otherwise, sizeOf(results) = limit.

Response samples

application/json
Copy
Expand all Collapse all
{
  • "count": 0,
  • "results":
    {
    }
}

Create Integration

Creates an integration

post /integration

SignalFx API endpoint.
Replace {REALM} with the name of your realm. For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.
To find your realm, go to your profile page in the SignalFx web UI.
If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration

Creates the integration object that SignalFx uses to connect with a monitoring, SSO, or alerting service. The steps for establishing a connection to a service differ for each type of service and may differ for individual services. Refer to the SignalFx Developers Guide for more information regarding individual services.
This API is only available to users who have administrative authorization. Each service has its own API model for creating an integration object.
NOTES:

  • To ensure security, SignalFx omits some authentication and authorization properties from response objects. The integration model description for a property tells you if it's omitted from responses.
  • In the response object for the POST method, the "enabled" property is always set to true.
query Parameters
skipValidation
boolean

Flag that controls how SignalFx validates an alert integration object. If true, SignalFx doesn't send a test notification.

header Parameters
Content-Type
required
string

Format of the request payload. The only allowed value is "application/json".

X-SF-TOKEN
required
string

Authentication token. Must be a session token (User API access token) associated with a SignalFx user that has administrative privileges.

Request Body schema: application/json

Model defining the properties that SignalFx uses to create the integration object. Each service that SignalFx integrates with has its own model.
NOTE: Because this is a request to create a new integration, you must specify the "type" and "name" properties:

  • "type" determines what type of integration SignalFx creates.
  • "name" provides your unique name for the integration.
created
integer <int64> (Created)

The creation date and time for the integration object, in Unix time UTC-relative. The system sets this value, and you can't modify it.

creator
string (Creator)

SignalFx-assigned user ID of the user that created the integration object. If the system created the object, the value is "AAAAAAAAAA". The system sets this value, and you can't modify it.

enabled
boolean (Enabled)

Flag that indicates the state of the integration object. If true, the integration is enabled. If false, the integration is disabled, and you must enable it by setting "enabled" to true in a PUT request that updates the object.
NOTE: SignalFx always sets the flag to true when you call POST /integration to create an integration.

id
string (IntegrationID)

SignalFx-assigned ID of an integration you create in the web UI or API. Use this property to retrieve an integration using the GET, PUT, or DELETE /integration/{id} endpoints or the GET /integration/validate{id}/ endpoint, as described in this topic.

lastUpdated
integer <int64> (LastUpdated)

The last time the integration was updated, in Unix time UTC-relative. This value is "read-only".

lastUpdatedBy
string (LastUpdatedBy)

SignalFx-assigned ID of the last user who updated the integration. If the last update was by the system, the value is "AAAAAAAAAA". This value is "read-only".

name
string (Name)

A human-readable label for the integration. This property helps you identify a specific integration when you're using multiple integrations for the same service.

type
required
string (Type)

Service that this integration object configures in SignalFx. This is an enumerated string that describes the service. SignalFx processes requests based on the type specified.
In addition, the "type" property controls OpenApi 3 validation. If you use a model for one service but specify the type for another service, OAS 3 validation programs may reject your request.
For data collection services, the allowed values are:

  • AWSCloudWatch
  • Azure
  • GCP
  • NewRelic

For SSO integrations, the allowed values are:

  • ADFS
  • AzureAD
  • Bitium
  • GoogleSaml
  • Okta
  • OneLogin
  • PingOne

For alerting services, the allowed values are:

  • BigPanda
  • Office365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • XMatters (note the capital "X")

Viewing request or response bodies

To see the request or response body format, find it in the following dropdown box. To see a full list, click the down arrow and navigate with the vertical scrollbar.

issuerUrl
any (IssuerUrl)

URL of the entity that issued the certificate for the SAML

metadata
string (Metadata)

File name of the SAML metadata XML file for the integration: FederationMetadata.xml

publicKey
string (PublicKey)

Contents of the certificate.pem file for the public key associated with the SAML integration

Responses

200

Successful creation of an integration object

Response Schema: application/json
created
integer <int64> (Created)

The creation date and time for the integration object, in Unix time UTC-relative. The system sets this value, and you can't modify it.

creator
string (Creator)

SignalFx-assigned user ID of the user that created the integration object. If the system created the object, the value is "AAAAAAAAAA". The system sets this value, and you can't modify it.

enabled
boolean (Enabled)

Flag that indicates the state of the integration object. If true, the integration is enabled. If false, the integration is disabled, and you must enable it by setting "enabled" to true in a PUT request that updates the object.
NOTE: SignalFx always sets the flag to true when you call POST /integration to create an integration.

id
string (IntegrationID)

SignalFx-assigned ID of an integration you create in the web UI or API. Use this property to retrieve an integration using the GET, PUT, or DELETE /integration/{id} endpoints or the GET /integration/validate{id}/ endpoint, as described in this topic.

lastUpdated
integer <int64> (LastUpdated)

The last time the integration was updated, in Unix time UTC-relative. This value is "read-only".

lastUpdatedBy
string (LastUpdatedBy)

SignalFx-assigned ID of the last user who updated the integration. If the last update was by the system, the value is "AAAAAAAAAA". This value is "read-only".

name
string (Name)

A human-readable label for the integration. This property helps you identify a specific integration when you're using multiple integrations for the same service.

type
required
string (Type)

Service that this integration object configures in SignalFx. This is an enumerated string that describes the service. SignalFx processes requests based on the type specified.
In addition, the "type" property controls OpenApi 3 validation. If you use a model for one service but specify the type for another service, OAS 3 validation programs may reject your request.
For data collection services, the allowed values are:

  • AWSCloudWatch
  • Azure
  • GCP
  • NewRelic

For SSO integrations, the allowed values are:

  • ADFS
  • AzureAD
  • Bitium
  • GoogleSaml
  • Okta
  • OneLogin
  • PingOne

For alerting services, the allowed values are:

  • BigPanda
  • Office365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • XMatters (note the capital "X")

Viewing request or response bodies

To see the request or response body format, find it in the following dropdown box. To see a full list, click the down arrow and navigate with the vertical scrollbar.

issuerUrl
any (IssuerUrl)

URL of the entity that issued the certificate for the SAML

metadata
string (Metadata)

File name of the SAML metadata XML file for the integration: FederationMetadata.xml

publicKey
string (PublicKey)

Contents of the certificate.pem file for the public key associated with the SAML integration

Request samples

application/json
Copy
Expand all Collapse all
{
  • "created": 1556361030000,
  • "creator": "string",
  • "enabled": true,
  • "id": "string",
  • "lastUpdated": 1556620230000,
  • "lastUpdatedBy": "string",
  • "name": "string",
  • "type": "ADFS",
  • "issuerUrl": null,
  • "metadata": "string",
  • "publicKey": "string"
}

Response samples

application/json
Copy
Expand all Collapse all
{
  • "created": 1556361030000,
  • "creator": "string",
  • "enabled": true,
  • "id": "string",
  • "lastUpdated": 1556620230000,
  • "lastUpdatedBy": "string",
  • "name": "string",
  • "type": "ADFS",
  • "issuerUrl": null,
  • "metadata": "string",
  • "publicKey": "string"
}

Validate Integration

Validates the integration specified in the {id} path parameter

get /integration/validate/{id}

SignalFx API endpoint.
Replace {REALM} with the name of your realm. For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.
To find your realm, go to your profile page in the SignalFx web UI.
If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration/validate/{id}

Validates the credentials of an existing integration.
Integrations such as AWS or GCP may have permission changes. Use this API to verify that the integration is still valid.
NOTE: This API doesn't require a request body, and doesn't return a response body.

path Parameters
id
required
string

SignalFx-assigned ID of the existing integration object that you want to validate

header Parameters
X-SF-TOKEN
required
string

Authentication token. Must be a session token (User API access token) associated with a SignalFx user that has administrative privileges.

Responses

200

Successful validation of the integration object

Delete Single Integration

Deletes an integration specified in the {id} path parameter

delete /integration/{id}

SignalFx API endpoint.
Replace {REALM} with the name of your realm. For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.
To find your realm, go to your profile page in the SignalFx web UI.
If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration/{id}

Deletes the integration object specified by the id path parameter.
NOTE: This API doesn't require a request body, and doesn't return a response body.

path Parameters
id
required
string

SignalFx-assigned ID of the existing integration object that you want to delete

header Parameters
X-SF-TOKEN
required
string

Authentication token. Must be a session token (User API access token) associated with a SignalFx user that has administrative privileges.

Responses

200

Successful update of the integration object

Retrieve Single Integration

Retrieves an integration specified in the {id} path parameter

get /integration/{id}

SignalFx API endpoint.
Replace {REALM} with the name of your realm. For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.
To find your realm, go to your profile page in the SignalFx web UI.
If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration/{id}

Retrieves the integration object specified by the id path parameter. NOTE: To ensure security, SignalFx omits some authentication and authorization properties from response objects. The integration model description for a property tells you if it's omitted from responses.

path Parameters
id
required
string

SignalFx-assigned ID of the existing integration object that you want to retrieve

header Parameters
X-SF-Token
required
string

Authentication token.

Responses

200

Successful retrieval of the specified integration object.
NOTE: If the request is well-formed but SignalFx can't find the object, the API still returns 200. In this case, the response body is empty.

Response Schema: application/json
created
integer <int64> (Created)

The creation date and time for the integration object, in Unix time UTC-relative. The system sets this value, and you can't modify it.

creator
string (Creator)

SignalFx-assigned user ID of the user that created the integration object. If the system created the object, the value is "AAAAAAAAAA". The system sets this value, and you can't modify it.

enabled
boolean (Enabled)

Flag that indicates the state of the integration object. If true, the integration is enabled. If false, the integration is disabled, and you must enable it by setting "enabled" to true in a PUT request that updates the object.
NOTE: SignalFx always sets the flag to true when you call POST /integration to create an integration.

id
string (IntegrationID)

SignalFx-assigned ID of an integration you create in the web UI or API. Use this property to retrieve an integration using the GET, PUT, or DELETE /integration/{id} endpoints or the GET /integration/validate{id}/ endpoint, as described in this topic.

lastUpdated
integer <int64> (LastUpdated)

The last time the integration was updated, in Unix time UTC-relative. This value is "read-only".

lastUpdatedBy
string (LastUpdatedBy)

SignalFx-assigned ID of the last user who updated the integration. If the last update was by the system, the value is "AAAAAAAAAA". This value is "read-only".

name
string (Name)

A human-readable label for the integration. This property helps you identify a specific integration when you're using multiple integrations for the same service.

type
required
string (Type)

Service that this integration object configures in SignalFx. This is an enumerated string that describes the service. SignalFx processes requests based on the type specified.
In addition, the "type" property controls OpenApi 3 validation. If you use a model for one service but specify the type for another service, OAS 3 validation programs may reject your request.
For data collection services, the allowed values are:

  • AWSCloudWatch
  • Azure
  • GCP
  • NewRelic

For SSO integrations, the allowed values are:

  • ADFS
  • AzureAD
  • Bitium
  • GoogleSaml
  • Okta
  • OneLogin
  • PingOne

For alerting services, the allowed values are:

  • BigPanda
  • Office365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • XMatters (note the capital "X")

Viewing request or response bodies

To see the request or response body format, find it in the following dropdown box. To see a full list, click the down arrow and navigate with the vertical scrollbar.

issuerUrl
any (IssuerUrl)

URL of the entity that issued the certificate for the SAML

metadata
string (Metadata)

File name of the SAML metadata XML file for the integration: FederationMetadata.xml

publicKey
string (PublicKey)

Contents of the certificate.pem file for the public key associated with the SAML integration

Response samples

application/json
Copy
Expand all Collapse all
{
  • "created": 1556361030000,
  • "creator": "string",
  • "enabled": true,
  • "id": "string",
  • "lastUpdated": 1556620230000,
  • "lastUpdatedBy": "string",
  • "name": "string",
  • "type": "ADFS",
  • "issuerUrl": null,
  • "metadata": "string",
  • "publicKey": "string"
}

Update Single Integration

Updates an integration specified in the {id} path parameter

put /integration/{id}

SignalFx API endpoint.
Replace {REALM} with the name of your realm. For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.
To find your realm, go to your profile page in the SignalFx web UI.
If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration/{id}

Updates the integration object specified by the id path parameter.
NOTE: To ensure security, SignalFx omits some authentication and authorization properties from response objects. The integration model description for a property tells you if it's omitted from responses.

path Parameters
id
required
string

SignalFx-assigned ID of the existing integration object that you want to update

query Parameters
skipValidation
boolean

Flag that controls how SignalFx validates an alert integration object. If true, SignalFx doesn't send a test notification.

header Parameters
Content-Type
required
string

Format of the request payload. The only allowed value is "application/json".

X-SF-TOKEN
required
string

Authentication token. Must be a session token (User API access token) associated with a SignalFx user that has administrative privileges.

Request Body schema: application/json

Model specifying the properties that SignalFx uses to update the integration object. Each service that SignalFx integrates with has its own model.
NOTE: For Office 365 integrations, you can only update the following properties:

  • "name"
  • "creator"
  • "created"
  • "lastUpdated"
  • "lastUpdatedBy"
  • "enabled"
  • "type"
    All of these fields are described in the IntegrationCommonPropertiesModel schema.
created
integer <int64> (Created)

The creation date and time for the integration object, in Unix time UTC-relative. The system sets this value, and you can't modify it.

creator
string (Creator)

SignalFx-assigned user ID of the user that created the integration object. If the system created the object, the value is "AAAAAAAAAA". The system sets this value, and you can't modify it.

enabled
boolean (Enabled)

Flag that indicates the state of the integration object. If true, the integration is enabled. If false, the integration is disabled, and you must enable it by setting "enabled" to true in a PUT request that updates the object.
NOTE: SignalFx always sets the flag to true when you call POST /integration to create an integration.

id
string (IntegrationID)

SignalFx-assigned ID of an integration you create in the web UI or API. Use this property to retrieve an integration using the GET, PUT, or DELETE /integration/{id} endpoints or the GET /integration/validate{id}/ endpoint, as described in this topic.

lastUpdated
integer <int64> (LastUpdated)

The last time the integration was updated, in Unix time UTC-relative. This value is "read-only".

lastUpdatedBy
string (LastUpdatedBy)

SignalFx-assigned ID of the last user who updated the integration. If the last update was by the system, the value is "AAAAAAAAAA". This value is "read-only".

name
string (Name)

A human-readable label for the integration. This property helps you identify a specific integration when you're using multiple integrations for the same service.

type
required
string (Type)

Service that this integration object configures in SignalFx. This is an enumerated string that describes the service. SignalFx processes requests based on the type specified.
In addition, the "type" property controls OpenApi 3 validation. If you use a model for one service but specify the type for another service, OAS 3 validation programs may reject your request.
For data collection services, the allowed values are:

  • AWSCloudWatch
  • Azure
  • GCP
  • NewRelic

For SSO integrations, the allowed values are:

  • ADFS
  • AzureAD
  • Bitium
  • GoogleSaml
  • Okta
  • OneLogin
  • PingOne

For alerting services, the allowed values are:

  • BigPanda
  • Office365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • XMatters (note the capital "X")

Viewing request or response bodies

To see the request or response body format, find it in the following dropdown box. To see a full list, click the down arrow and navigate with the vertical scrollbar.

issuerUrl
any (IssuerUrl)

URL of the entity that issued the certificate for the SAML

metadata
string (Metadata)

File name of the SAML metadata XML file for the integration: FederationMetadata.xml

publicKey
string (PublicKey)

Contents of the certificate.pem file for the public key associated with the SAML integration

Responses

200

Successful update of the integration object

Response Schema: application/json
created
integer <int64> (Created)

The creation date and time for the integration object, in Unix time UTC-relative. The system sets this value, and you can't modify it.

creator
string (Creator)

SignalFx-assigned user ID of the user that created the integration object. If the system created the object, the value is "AAAAAAAAAA". The system sets this value, and you can't modify it.

enabled
boolean (Enabled)

Flag that indicates the state of the integration object. If true, the integration is enabled. If false, the integration is disabled, and you must enable it by setting "enabled" to true in a PUT request that updates the object.
NOTE: SignalFx always sets the flag to true when you call POST /integration to create an integration.

id
string (IntegrationID)

SignalFx-assigned ID of an integration you create in the web UI or API. Use this property to retrieve an integration using the GET, PUT, or DELETE /integration/{id} endpoints or the GET /integration/validate{id}/ endpoint, as described in this topic.

lastUpdated
integer <int64> (LastUpdated)

The last time the integration was updated, in Unix time UTC-relative. This value is "read-only".

lastUpdatedBy
string (LastUpdatedBy)

SignalFx-assigned ID of the last user who updated the integration. If the last update was by the system, the value is "AAAAAAAAAA". This value is "read-only".

name
string (Name)

A human-readable label for the integration. This property helps you identify a specific integration when you're using multiple integrations for the same service.

type
required
string (Type)

Service that this integration object configures in SignalFx. This is an enumerated string that describes the service. SignalFx processes requests based on the type specified.
In addition, the "type" property controls OpenApi 3 validation. If you use a model for one service but specify the type for another service, OAS 3 validation programs may reject your request.
For data collection services, the allowed values are:

  • AWSCloudWatch
  • Azure
  • GCP
  • NewRelic

For SSO integrations, the allowed values are:

  • ADFS
  • AzureAD
  • Bitium
  • GoogleSaml
  • Okta
  • OneLogin
  • PingOne

For alerting services, the allowed values are:

  • BigPanda
  • Office365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • XMatters (note the capital "X")

Viewing request or response bodies

To see the request or response body format, find it in the following dropdown box. To see a full list, click the down arrow and navigate with the vertical scrollbar.

issuerUrl
any (IssuerUrl)

URL of the entity that issued the certificate for the SAML

metadata
string (Metadata)

File name of the SAML metadata XML file for the integration: FederationMetadata.xml

publicKey
string (PublicKey)

Contents of the certificate.pem file for the public key associated with the SAML integration

Request samples

application/json
Copy
Expand all Collapse all
{
  • "created": 1556361030000,
  • "creator": "string",
  • "enabled": true,
  • "id": "string",
  • "lastUpdated": 1556620230000,
  • "lastUpdatedBy": "string",
  • "name": "string",
  • "type": "ADFS",
  • "issuerUrl": null,
  • "metadata": "string",
  • "publicKey": "string"
}

Response samples

application/json
Copy
Expand all Collapse all
{
  • "created": 1556361030000,
  • "creator": "string",
  • "enabled": true,
  • "id": "string",
  • "lastUpdated": 1556620230000,
  • "lastUpdatedBy": "string",
  • "name": "string",
  • "type": "ADFS",
  • "issuerUrl": null,
  • "metadata": "string",
  • "publicKey": "string"
}