Skip to main content

 

Cisco Meraki Documentation

Infoblox Endpoint Target

Infoblox Endpoint Target

Infoblox Endpoint targets enable integration with Infoblox Universal DDI and Threat Defense APIs. By configuring an Infoblox Endpoint target, you can use workflows to send API requests to the Infoblox cloud endpoint and automate DDI-related operations.

Infoblox Endpoint targets require Infoblox Token-Based Credentials account keys and are used with Infoblox workflow activities, including the Generic DDI API Request activity.

Before You Begin

Before adding Infoblox as a target type in Workflows, ensure that you have:

  • Access to an Infoblox account with permission to use the required Universal DDI or Threat Defense APIs.

  • An Infoblox API key for authentication.

  • The Infoblox API host name for your environment, such as csp.infoblox.com.

Creating Infoblox Targets

Perform the following steps to create a new Infoblox target:

  1. From the left navigation menu, click Automation > Targets.

  2. Click New Target.

  3. From the Target Type drop-down list, choose Infoblox Endpoint.

  4. Enter a unique display name for the target in the Display Name field and a brief description in the Description field.

  5. In the Account Keys area, click the Default Account Keys drop-down list and choose an existing Infoblox Token-Based Credentials account key, or select Add New to create a new account key.

  6. In the Infoblox area, enter the following information:

    • Protocol: Choose HTTPS.

    • Host/IP Address: Enter the host name for the Infoblox API endpoint, such as csp.infoblox.com.

    • Port: Enter the port number for the Infoblox API endpoint. The default HTTPS port is 443.

  7. In the Proxy area, enter the URL, Username, and Password for your proxy server if required.

  8. The Proxy Bypass List allows you to provide a list of hosts to exclude from the proxy. Use the Ignore Proxy toggle to display or hide proxy settings.

  9. Click Save to save the target.

After the target is saved, select it in an Infoblox workflow activity, such as Generic DDI API Request, and provide the relative API path and request details required for the Infoblox API operation.

  • Was this article helpful?