Ready to Try?
View Categories

Endpoints for Connectors and Connector Profiles

You can use the Lucidum API to:

  • Retrieve a list of connectors and the bridge name, display name, description, group, and status of each connector

  • Retrieve configuration details about a single connector, including bridge name, display name, description, group, status, and additional configuration data

  • Create a connector profile

  • Retrieve details about all connector profiles, including the bridge name, display name, profile name, description, and configuration data

  • Retrieve details about a single connector profile, including the bridge name, display name, profile name, description, and configuration data

  • Delete a connector profile, using the DELETE method to remove a connector profile

  • Test a connector

  • Retrieve the test results for a connector, including the test status and the status of each service

The following sections describe the endpoints for these actions.

Headers #

Requests to the endpoints in the Lucidum API v2 must also include a header with:

Retrieve the List of Connectors: /CMDB/v2/connector #

This endpoint queries Lucidum for the list of all connectors. This endpoint returns:

  • an entry for each connector

  • the bridge name (connector name), display name, description, group, and status of each connector

Endpoint

Method

Parameters in URL

/CMDB/v2/connector

GET

  • None

Example cURL Request #

curl --location 'https://test.dev.luciduminc.net/CMDB/v2/connector/' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer tVgkmKJNTWhxECfHNfTb'

  • Line 1. The cURL call. The method defaults to GET. The URL is host name plus the endpoint for the connector API.

  • Line 2. The header specifies to return results in JSON.

  • Line 3. The header specifies to use a Bearer Token for authentication and provides the bearer token.

Example Response #

The response includes thousands of lines. Here is an abbreviated response that shows the first three connector records:

{
    “connectors”: [
        {
            “connector_name”: “api”,
            “bridge_name”: “ad_ldap”,
            “display_name”: “Microsoft Active Directory (AD)”,
            “description”: “Microsoft Active Directory (AD) provides a single point of control for managing users, computers, groups, and other resources on a network. Active Directory uses a structured data store as the basis for a logical, hierarchical organization of directory information.”,
            “group”: “Identity Access Management”,
            “status”: “available”
        },
        {
            “connector_name”: “api”,
            “bridge_name”: “addigy”,
            “display_name”: “Addigy”,
            “description”: “Addigy is a cloud-based, multi-tenant mobile device management solution that manages macOS, iOS, iPadOS, and iOS devices.”,
            “group”: “Asset Management”,
            “status”: “available”
        },
        {
            “connector_name”: “api”,
            “bridge_name”: “artifactory”,
            “display_name”: “Artifactory”,
            “description”: “JFrog Artifactory is a universal DevOps solution providing end-to-end automation and management of binaries and artifacts through the application delivery process that improves productivity across your development ecosystem.”,
            “group”: “Code Management”,
            “status”: “available”
        },

Retrieve Configuration Details About a Single Connector: /CMDB/v2/connector/config #

This endpoint queries Lucidum for configuration details about a single connector. This endpoint returns:

  • an entry for each connector

  • the bridge name (connector name), display name, description, group, and status of each connector

  • the configured fields for the connector

    NOTE: Credentials are not returned in the API.

Endpoint

Method

Parameters in URL

/CMDB/v2/connector/config

GET
  • connector_name=api
  • bridge_name=<bridge name of connector>
NOTE: To find the bridge_name of a connector, you can use the /CMDB/v2/connector endpoint and search the results for the connector you are interested in.

Example cURL Request #

curl --location 'https://test.dev.luciduminc.net/CMDB/v2/connector/config?connector_name=api&bridge_name=datadog' \
--header 'Content-Type: application/json' \
-header 'Authorization: Bearer tVgkmKJNTWhxECfHNfTb'

  • Line 1. The cURL call. If not method is specified, the method defaults to GET. The URL is host name plus the endpoint for the connector API.

  • Line 1. The “?” (question mark) character specifies that all the text to the right of the character is a parameter.

  • Line 1. connector_name=api is required. This parameter is identical for all connectors.

  • Line 1. The “&” (ampersand) character specifies that the test to the right of the character is an additional parameter.

  • Line 1. bridge_name=datadog. This parameter specifies the connector to retrieve configuration information for.

    NOTE: To find the bridge_name of a connector, you can use the /CMDB/v2/connector endpoint and search the results for the connector you are interested in.

  • Line 2. The header specifies to return results in JSON.

  • Line 3. The header specifies to use a Bearer Token for authentication and provides the bearer token.

Example Response #

The response looks like this:

NOTE: Credentials are not returned in the API.

{
    “connector_name”: “api”,
    “bridge_name”: “datadog”,
    “display_name”: “Datadog Enterprise”,
    “description”: “Datadog allows observability for cloud-scale applications, providing monitoring of servers, databases, tools, and services, through a SaaS-based data analytics platform.”,
    “group”: “Monitoring”,
    “status”: “available”,
    “config”: {
        “url”: “https://api.datadoghq.com”,
        “app_key”: “”,
        “api_key”: “”,
        “verify_ssl”: false,
        “field_metadata”: {
            “app_key”: “encrypt;required”,
            “api_key”: “encrypt;required”
        },
        “field_display”: {
            “url”: {
                “display_name”: “URL”,
                “description”: “The URL of the Datadog API, default value is https://api.datadoghq.com”
            },
            “app_key”: {
                “display_name”: “App Key”,
                “description”: “Datadog application key”
            },
            “api_key”: {
                “display_name”: “API Key”,
                “description”: “Datadog API key”
            },
            “verify_ssl”: {
                “display_name”: “Verify SSL”,
                “description”: “Toggle on/off validation of SSL certificate”
            }
        }
    }
}

Create a Profile for a Connector: /CMDB/v2/connector/profile #

This endpoint creates a new profile for a connector. You must test the profile after creation. This endpoint creates but does not test the new profile.

NOTE: Certain connectors, like the Google Cloud Platform connector or the ADP connector, require you to upload a file when creating a profile. You cannot create profiles for these connectors with API v2.

Method

Parameters in URL

/CMDB/v2/connector/profile

POST
  • connector_name: api
  • bridge_name: <bridge name of connector>
  • profile_name: <name for new profile>
  • url: <url for the connector third-party API>
  • fields required by config.field_metadata

To determine the field required by config.field_metadata:

Retrieve data from the endpoint /CMDB/v2/connector/config?connector_name=api&bridge_name=<bridge name for connector>.

NOTE: To find the bridge_name of a connector, you can use the /CMDB/v2/connector endpoint and search the results for the connector you are interested in.

Finding config.field_metadata #

To find the config.field_metadata fields to create a profile, you need to look at the configuration information for the connector.

For example, for the Datadog connector, call the endpoint /CMDB/v2/connector/config?connector_name=api&bridge_name=datadog

The results look like this:

{
    “connector_name”: “api”,
    “bridge_name”: “datadog”,
    “display_name”: “Datadog Enterprise”,
    “description”: “Datadog allows observability for cloud-scale applications, providing monitoring of servers, databases, tools, and services, through a SaaS-based data analytics platform.”,
    “group”: “Monitoring”,
    “status”: “available”,
    “config”: {
        “url”: “https://api.datadoghq.com”,
        “app_key”: “”,
        “api_key”: “”,
        “verify_ssl”: false,
        “field_metadata”: {
            “app_key”: “encrypt;required”,
            “api_key”: “encrypt;required”
      },
        “field_display”: {
            “url”: {
                “display_name”: “URL”,
                “description”: “The URL of the Datadog API, default value is https://api.datadoghq.com”
            },
            “app_key”: {
                “display_name”: “App Key”,
                “description”: “Datadog application key”
            },
            “api_key”: {
                “display_name”: “API Key”,
                “description”: “Datadog API key”
            },
            “verify_ssl”: {
                “display_name”: “Verify SSL”,
                “description”: “Toggle on/off validation of SSL certificate”
            }
        }
    }
}

  • Under the config section, find the section called field_metadata.

  • Note that the app_key and api_key fields are noted as required.

  • This means that you must include these two fields when creating a profile for the Datadog connector.

Example cURL Request #

curl --request POST --location 'https://test.dev.luciduminc.net/CMDB/v2/connector/profile' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer tVgkmKJNTWhxECfHNfTb' \
--data '{
"connector_name": "api",
"bridge_name": "datadog",
"profile_name": "customer_support",
"url": "https://api.datadoghq.com",
"app_key": "4573000511cec73cb26c95efc7fbc5bcb79ad855",
"api_key": "cdcb738d08d13ffa6233811f0b22eae5",
}'

  • Line 1. The cURL call. We specified “–request POST” so we can send data to Lucidum. The URL is host name plus the endpoint for the connector API.

  • Line 1. The The “\” (backslash) at the end of a line indicates to continue the cURL command on the next line and process all the lines as a single request.

  • Line 2. The header specifies to return results in JSON.

  • Line 3. The header specifies to use a Bearer Token for authentication and provides the bearer token.

  • Line 4. The data to send to Lucidum.

  • Line 5. “connector_name”: “api”  is required. This parameter is identical for all connectors.

  • Line 6. “bridge_name”: “datadog” This parameter specifies the connector to create a profile for.

    NOTE: To find the bridge_name of a connector, you can use the /CMDB/v2/connector endpoint and search the results for the connector you are interested in.

  • Line 7.  “profile_name”: “customer_support”. The name of the new profile.

  • Line 8. “url”: “https://api.datadoghq.com”. The optional URL for the Datadog API.

  • Line 9. “app_key”: “4573000511cec73cb26c95efc7fbc5bcb79ad855”. The required app_key for the Datadog profile.

  • Line 10. “api_key”: “cdcb738d08d13ffa6233811f0b22eae5”. The required api_key for the Datadog profile..

Example Response #

The response looks like this:

{
    “url”: “https://api.datadoghq.com”,
    “app_key”: “**************************”,
    “api_key”: “**************************”,
    “field_metadata”: {
        “app_key”: “encrypt;required”,
        “api_key”: “encrypt;required”
    },
    “field_display”: {
        “url”: {
            “display_name”: “URL”,
            “description”: “The URL of the Datadog API, default value is https://api.datadoghq.com”
        },
        “app_key”: {
            “display_name”: “App Key”,
            “description”: “Datadog application key”
        },
        “api_key”: {
            “display_name”: “API Key”,
            “description”: “Datadog API key”
        },
        “verify_ssl”: {
            “display_name”: “Verify SSL”,
            “description”: “Toggle on/off validation of SSL certificate”
        }
    },
    “active”: true,
    “description”: “Datadog allows observability for cloud-scale applications, providing monitoring of servers, databases, tools, and services, through a SaaS-based data analytics platform.”,
    “display_name”: “Datadog Enterprise”,
    “status”: “available”,
    “group”: “Monitoring”,
    “connector_name”: “api”,
    “bridge_name”: “datadog”,
    “profile_name”: “customer_support”,
    “modified_time”: “2024-09-24T14:59:42.476652Z”,
    “services_list”: [
        {
            “platform”: “api”,
            “type”: “user_info”,
            “display_name”: “Datadog User”,
            “service”: “datadog_user”,
            “activity”: true,
            “status”: “FAIL”,
            “message”: “not tested”
        },
        {
            “platform”: “api”,
            “type”: “asset_info”,
            “display_name”: “Datadog Host”,
            “service”: “datadog_host”,
            “activity”: true,
            “status”: “FAIL”,
            “message”: “not tested”
        },
        {
            “platform”: “api”,
            “type”: “asset_info”,
            “display_name”: “Datadog Container”,
            “service”: “datadog_container”,
            “activity”: true,
            “status”: “FAIL”,
            “message”: “not tested”
        }
    ],
    “profile_id”: “66f2d3de9cb7671a2c4b0c75”
}

Retrieve the List of Profiles for All Connectors: /CMDB/v2/connector/profile #

This endpoint queries Lucidum for the list of all profiles for all connectors. This endpoint returns:

  • an entry for each connector

  • the bridge name (connector name), display name, description, group, and status of each connector

Endpoint

Method

Parameters in URL

/CMDB/v2/connector/profile

GET

  • None

Example cURL Request #

curl --location 'https://test.dev.luciduminc.net/CMDB/v2/connector/profile' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer tVgkmKJNTWhxECfHNfTb'

  • Line 1. The cURL call. If no method is specified, the method defaults to GET. The URL is host name plus the endpoint for the connector API.

  • Line 2. The header specifies to return results in JSON.

  • Line 3. The header specifies to use a Bearer Token for authentication and provides the bearer token.

Example Response #

The response includes thousands of lines. Here is an abbreviated response that shows a single connector profile:

{
    “connectorProfiles”: [
        {
            “app_id”: “***************************”,
            “app_secret”: “***************************”,
            “tenant_id”: “***************************”,
            “url”: “https://fef.amsua0602.manage.microsoft.com/ReportingService/DataWarehouseFEService/”,
            “field_metadata”: {
                “app_id”: “required”,
                “app_secret”: “encrypt;required”,
                “tenant_id”: “required”,
                “url”: “required”
            },
            “field_display”: {
                “url”: {
                    “display_name”: “URL”,
                    “description”: “Microsoft intune URL. For example, https://<intune subdomain>.manage.microsoft.com/ReportingService/DataWarehouseFEService/”
                },
                “app_id”: {
                    “display_name”: “Client ID”,
                    “description”: “Client ID for the application”
                },
                “app_secret”: {
                    “display_name”: “Client secret”,
                    “description”: “Client secret for the application”
                },
                “tenant_id”: {
                    “display_name”: “Tenant ID”,
                    “description”: “Microsoft Azure tenant ID”
                }
            },
            “status”: “available”,
            “bridge_name”: “intune”,
            “connector_name”: “api”,
            “display_name”: “Microsoft Intune”,
            “description”: “Microsoft Intune is a cloud-based service that focuses on mobile device management (MDM) and mobile application management (MAM).”,
            “active”: true,
            “profile_name”: “Default profile”,
            “services_list”: [
                {
                    “connection”: “intune”,
                    “connector”: “api”,
                    “service”: “intune_device”,
                    “status”: “OK”,
                    “activity”: true
                },
                {
                    “connection”: “intune”,
                    “connector”: “api”,
                    “service”: “intune_user”,
                    “status”: “OK”,
                    “activity”: true
                }
            ],
            “profile_id”: “62268b697ad01232db4bc3a7”
        },

Retrieve a Single Profile for a Single Connector: /CMDB/v2/connector/profile #

This endpoint queries Lucidum for details about a single profile for a single connector.

Endpoint

Method

Parameters in URL

/CMDB/v2/connector/profile

GET
  • connector_name=api
  • bridge_name=<bridge name of connector>
  • profile_name=<profile name>

NOTE: To find the bridge_name of a connector, you can use the /CMDB/v2/connector endpoint and search the results for the connector you are interested in.</0>

NOTE: To find the profile_name for a connector, you can use the /CMDB/v2/connector/profile endpoint and search the results for the profile you are interested in.

Example cURL Request #

curl --location 'https://test.dev.luciduminc.net/CMDB/v2/connector/profile?connector_name=api&bridge_name=datadog&profile_name=api profile 1' \
--header 'Content-Type: application/json' \
-header 'Authorization: Bearer tVgkmKJNTWhxECfHNfTb'

  • Line 1. The cURL call. If no method is specified, the method defaults to GET. The URL is host name plus the endpoint for the connector API.

  • Line 1. The “?” (question mark) character specifies that all the text to the right of the character is a parameter.

  • Line 1. connector_name=api is required. This parameter is identical for all connectors.

  • Line 1. The “&” (ampersand) character specifies that the test to the right of the character is an additional parameter.

  • Line 1. bridge_name=datadog. This parameter specifies the connector to retrieve information from.

    NOTE: To find the bridge_name of a connector, you can use the /CMDB/v2/connector endpoint and search the results for the connector you are interested in.

  • Line 1. profile_name=api profile 1. This parameter specifies the profile to retrieve information from.

    NOTE: To find the profile_name for a connector, you can use the /CMDB/v2/connector/profile endpoint and search the results for the profile you are interested in.

  • Line 2. The header specifies to return results in JSON.

  • Line 3. The header specifies to use a Bearer Token for authentication and provides the bearer token.

Example Response #

{
    “connectorProfiles”: [
        {
            “url”: “https://api.datadoghq.com”,
            “app_key”: “gAAAAABm1y5ovo7UY-gPbw-6J0sC-7jEL_UkLsbemskIxJx9qHKXE2M4uIy9S4DKW4xW1CsYZNKKgxqJLOsjJnw_KRp4rRmR80Z3dxBwbQ5YPiRb23obKmI_sj0avPm2AnJ6Ebg-qOQ9”,
            “api_key”: “gAAAAABm1y5oJP_a8uo4IZknMGrZesG8zgja3KG5AAzFrveV2xakU88tGIOLJkk8jLuW_QaCbDM6u4mbLjruiix-BmyXhCzRGvibP1w13fS38c1rHj2Zdn7MTRKk-sKWKUrmlF7vjA_M”,
            “verify_ssl”: false,
            “field_metadata”: {
                “app_key”: “encrypt;required”,
                “api_key”: “encrypt;required”
            },
            “field_display”: {
                “url”: {
                    “display_name”: “URL”,
                    “description”: “The URL of the Datadog API, default value is https://api.datadoghq.com”
                },
                “app_key”: {
                    “display_name”: “App Key”,
                    “description”: “Datadog application key”
                },
                “api_key”: {
                    “display_name”: “API Key”,
                    “description”: “Datadog API key”
                },
                “verify_ssl”: {
                    “display_name”: “Verify SSL”,
                    “description”: “Toggle on/off validation of SSL certificate”
                }
            },
            “active”: true,
            “description”: “Datadog allows observability for cloud-scale applications, providing monitoring of servers, databases, tools, and services, through a SaaS-based data analytics platform.”,
            “display_name”: “Datadog Enterprise”,
            “status”: “available”,
            “group”: “Monitoring”,
            “connector_name”: “api”,
            “bridge_name”: “datadog”,
            “profile_name”: “api profile 1”,
            “modified_time”: “2024-09-03T15:42:32.778+00:00”,
            “services_list”: [
                {
                    “platform”: “api”,
                    “type”: “user_info”,
                    “display_name”: “Datadog User”,
                    “service”: “datadog_user”,
                    “activity”: true,
                    “status”: “OK”,
                    “message”: “success”
                },
                {
                    “platform”: “api”,
                    “type”: “asset_info”,
                    “display_name”: “Datadog Host”,
                    “service”: “datadog_host”,
                    “activity”: true,
                    “status”: “OK”,
                    “message”: “success”
                },
                {
                    “platform”: “api”,
                    “type”: “asset_info”,
                    “display_name”: “Datadog Container”,
                    “service”: “datadog_container”,
                    “activity”: true,
                    “status”: “OK”,
                    “message”: “success”
                }
            ],
            “profile_id”: “66d72e68ccb4dc5bc98c286e”
        }
    ]
}

Delete a Single Profile for a Single Connector: /CMDB/v2/connector/profile #

This endpoint deletes a single profile for a single connector.

Endpoint

Method

Parameters in URL

/CMDB/v2/connector/profile

DELETE
  • connector_name=api
  • bridge_name=<bridge name of connector>
  • profile_name=<profile name>

NOTE: To find the bridge_name of a connector, you can use the /CMDB/v2/connector endpoint and search the results for the connector you are interested in.

NOTE: To find the profile_name for a connector, you can use the /CMDB/v2/connector/profile endpoint and search the results for the profile you are interested in.

Example cURL Request #

curl --request DELETE --location 'https://test.dev.luciduminc.net/CMDB/v2/connector/profile?connector_name=api&bridge_name=datadog&profile_name=api profile 1' \
--header 'Content-Type: application/json' \
-header 'Authorization: Bearer tVgkmKJNTWhxECfHNfTb'

  • Line 1. The cURL call. We specified “–request DELETE ” so we can delete a profile. The URL is host name plus the endpoint for the connector API.

  • Line 1. The “?” (question mark) character specifies that all the text to the right of the character is a parameter.

  • Line 1. connector_name=api is required. This parameter is identical for all connectors.

  • Line 1. The “&” (ampersand) character specifies that the test to the right of the character is an additional parameter.

  • Line 1. bridge_name=datadog. This parameter specifies the connector to delete information from.

    NOTE: To find the bridge_name of a connector, you can use the /CMDB/v2/connector endpoint and search the results for the connector you are interested in.

  • Line 1. profile_name=api profile 1. This parameter specifies the profile to delete.

    NOTE: To find the profile_name for a connector, you can use the /CMDB/v2/connector/profile endpoint and search the results for the profile you are interested in.

  • Line 2. The header specifies to return results in JSON.

  • Line 3. The header specifies to use a Bearer Token for authentication and provides the bearer token.

Example Response #

{
    “removed”: true
}

Test a Connector: /CMDB/v2/connector/test/async #

This endpoint tests a single connector using a single profile.

Method

Parameters in URL

/CMDB/v2/connector/test/async

POST
  • connector_name: api
  • bridge_name: <bridge name of connector>
  • profile_name: <name for new profile>a

NOTE: To find the bridge_name of a connector, you can use the /CMDB/v2/connector endpoint and search the results for the connector you are interested in.

NOTE: To find the profile_name for a connector, you can use the /CMDB/v2/connector/profile endpoint and search the results for the profile you are interested in.

Example cURL Request #

curl --request POST --location 'https://test.dev.luciduminc.net/CMDB/v2/connector/test/async' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer tVgkmKJNTWhxECfHNfTb' \
--data '{
"connector_name": "api",
"bridge_name": "datadog",
"profile_name": "customer_support",
}'

  • Line 1. The cURL call. We specified “–request POST” so we can send data to Lucidum. The URL is host name plus the endpoint for the connector API.

  • Line 1. The The “\” (backslash) at the end of a line indicates to continue the cURL command on the next line and process all the lines as a single request.

  • Line 2. The header specifies to return results in JSON.

  • Line 3. The header specifies to use a Bearer Token for authentication and provides the bearer token.

  • Line 4. The data to send to Lucidum.

  • Line 5. “connector_name”: “api”  is required. This parameter is identical for all connectors.

  • Line 6. “bridge_name”: “datadog” This parameter specifies the connector to create a profile for.

    NOTE: To find the bridge_name of a connector, you can use the /CMDB/v2/connector endpoint and search the results for the connector you are interested in.

  • Line 7. profile_name: “api profile 1”. This parameter specifies the profile to delete.

    NOTE: To find the profile_name for a connector, you can use the /CMDB/v2/connector/profile endpoint and search the results for the connector you are interested in.

Example Response #

{
    “traceId”: “66f418ec69a1e873b8ef4f57”
}

Viewing Test Results: /CMDB/v2/connector/test/result #

This endpoint tests a single connector using a single profile.

Method

Parameters in URL

/CMDB/v2/connector/test/result

GET
  • traceId: <traceId returned by /CMDB/v2/connector/test/async endpoint>

NOTE: To find the traceID for test results, you can use the /CMDB/v2/connector/test/async endpoint. This endpoint returns the traceID.

Example cURL Request #

curl --location 'https://test.dev.luciduminc.net/CMDB/v2/connector/test/result?traceId=66f418ec69a1e873b8ef4f57' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer tVgkmKJNTWhxECfHNfTb' \

  • Line 1. The cURL call. If no method is specified, the method defaults to GET. The URL is host name plus the endpoint for the connector API.

  • Line 1. The “?” (question mark) character specifies that all the text to the right of the character is a parameter.

  • Line 1. traceId=66f418ec69a1e873b8ef4f57. This parameter specifies the test results to display.

    NOTE: To find the traceID for test results, you can use the /CMDB/v2/connector/test/async endpoint. This endpoint returns the traceID.

  • The The “\” (backslash) at the end of a line indicates to continue the cURL command on the next line and process all the lines as a single request.

  • Line 2. The header specifies to return results in JSON.

  • Line 3. The header specifies to use a Bearer Token for authentication and provides the bearer token.

Example Response #

{
    “connector_name”: “api”,
    “bridge_name”: “datadog”,
    “trace_id”: “66f41e0b69a1e873b8ef4f62”,
    “profile_db_id”: “66d72e68ccb4dc5bc98c286e”,
    “test_result”: [
        {
            “name”: “datadog_user”,
            “status”: “FAIL”,
            “message”: “403 Client Error: Forbidden for url: https://api.datadoghq.com/api/v2/users?page%5Bnumber%5D=0&page%5Bsize%5D=2”,
            “details”: [
                {
                    “name”: “connection”,
                    “status”: “OK”,
                    “message”: “success”
                },
                {
                    “name”: “http_error”,
                    “status”: “FAIL”,
                    “message”: “403 Client Error: Forbidden for url: https://api.datadoghq.com/api/v2/users?page%5Bnumber%5D=0&page%5Bsize%5D=2”
                }
            ],
            “display_name”: “Datadog User”
        },
        {
            “name”: “datadog_host”,
            “status”: “FAIL”,
            “message”: “403 Client Error: Forbidden for url: https://api.datadoghq.com/api/v2/hosts?start=0&count=5”,
            “details”: [
                {
                    “name”: “connection”,
                    “status”: “OK”,
                    “message”: “success”
                },
                {
                    “name”: “http_error”,
                    “status”: “FAIL”,
                    “message”: “403 Client Error: Forbidden for url: https://api.datadoghq.com/api/v2/hosts?start=0&count=5”
                }
            ],
            “display_name”: “Datadog Host”
        },
        {
            “name”: “datadog_container”,
            “status”: “FAIL”,
            “message”: “403 Client Error: Forbidden for url: https://api.datadoghq.com/api/v2/containers?page%5Bsize%5D=5”,
            “details”: [
                {
                    “name”: “connection”,
                    “status”: “OK”,
                    “message”: “success”
                },
                {
                    “name”: “http_error”,
                    “status”: “FAIL”,
                    “message”: “403 Client Error: Forbidden for url: https://api.datadoghq.com/api/v2/containers?page%5Bsize%5D=5”
                }
            ],
            “display_name”: “Datadog Container”
        }
    ],
    “last_tested_at”: “2024-09-25T14:28:55.307+00:00”,
    “status”: “done”
}

What are your Feelings

Quick LInks

Linkedin Youtube X-twitter Facebook

@ 2025 Lucidum, Inc. Design By Sandman Studios

SOLUTIONS

COMPANY

RESOURCES

Solutions

COMPANY

Resource Library