# DNSFilter integrations: networks and policies

> Create a network, add domains to allow lists and create a user in DNSFilter.

**Canonical page:** https://tray.ai/connectors/dnsfilter-integrations/
**Categories:** Security and compliance
**Connects through:** HTTP Connector

## Overview

DNSFilter is a DNS-based web filtering and threat protection service that blocks malicious and unwanted websites across networks and devices. Tray.ai connects to DNSFilter through the HTTP Connector, so your workflows can call the DNSFilter API alongside the rest of your stack.

## Use cases

### Networks

Read, create, and update networks in DNSFilter from any Tray.ai workflow. The DNSFilter API covers calls such as list networks and create a network.

- List networks
- Create a network
- Get a network

### Policies

Create and delete policies in DNSFilter from any Tray.ai workflow. The DNSFilter API covers calls such as add domains to allow lists and add domains to block lists.

- Add domains to allow lists
- Add domains to block lists
- Remove domains from allow lists

### Organizations

Read, create, update, and delete organizations in DNSFilter from any Tray.ai workflow. The DNSFilter API covers calls such as list organizations and create an organization.

- List organizations
- Create an organization
- Update an organization

### Organization users

Read, create, update, and delete organization users in DNSFilter from any Tray.ai workflow. The DNSFilter API covers calls such as list users and create a user.

- List users
- Create a user
- Update a user

### Block pages

Read, create, update, and delete block pages in DNSFilter from any Tray.ai workflow. The DNSFilter API covers calls such as list block pages and create a block page.

- List block pages
- Create a block page
- Update a block page

### Domains

Read and manage domains in DNSFilter from any Tray.ai workflow. The DNSFilter API covers calls such as look up a domain and bulk look up domains.

- Look up a domain
- Bulk look up domains
- Suggest a threat

## Challenges Tray.ai solves

### Keeping DNSFilter credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store DNSFilter credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the DNSFilter API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the DNSFilter API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to DNSFilter?

Yes. Tray.ai connects to DNSFilter through the HTTP Connector, which calls the DNSFilter API directly. Any call the DNSFilter API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with DNSFilter?

The DNSFilter API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated DNSFilter connector?

DNSFilter runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated DNSFilter connector from the DNSFilter API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/