DNSFilter icon

DNSFilter

**Note:** If you are a distributor integrating with DNSFilter, please check out our [Distributors Development Guide](/docs/distributors).### Authentication- Authentication is required for most, but not all, endpoints.- Authentication is done by setting the `Authorization` request header. The header value is the API key itself. For example: `Authorization: eyJ...`- An API key can be obtained through the DNSFilter dashboard under Account Settings. For additional information see [this KB article](https://help.dnsfilter.com/hc/en-us/articles/21169189058323-API-Tokens).### Rate Limiting- All endpoints are rate limited.- The limits may vary by endpoint, but are generally consistent.- When the rate limit is exceeded the API will return the standard `429` HTTP status.- The following headers will also be provided in the response: `Retry-After`, `RateLimit-Policy`, `RateLimit`, `RateLimit-Limit`, `RateLimit-Remaining`, `RateLimit-Reset`. For details on the values of these headers, see the following articles [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After), [here](https://www.ietf.org/archive/id/draft-ietf-httpapi-ratelimit-headers-08.html), and [here](https://www.ietf.org/archive/id/draft-polli-ratelimit-headers-05.html).- For additional information see [this KB article](https://help.dnsfilter.com/hc/en-us/articles/38202811088403-API-Rate-Limits).### Error Handling- The API uses standard HTTP status codes to indicate success or failure.- For _V1_ endpoints the response format is: ```json { "error": "string", "type": "string(optional)" } ```- For _V2_ endpoints the response format is: ```json { "error": { "message": "string", "type": "string(optional)" } } ```### PaginationFor the _V1_ endpoints, the pagination parameters are nested. That is to say,if passed as JSON they look like this: `{"page[number]": 1, "page[size]": 10}`.To pass this information in the URL query string, it would be formatted likethis: `...?page%5Bnumber%5D=1&page%5Bsize%5D=10`.In this guide, the UI will indicate that `page` is an `object` and if youwant to set values when trying the request, you must enter it as if it wasthe JSON above.### A Quick ExampleThe following will return information about the currentlyauthenticated user.```bash% curl -H 'Authorization: ***' https://api.dnsfilter.com/v1/users/self{ "data": { "id": "12345", "type": "users", "attributes": { "name": "John Doe", "email": "john@example.com", ...additional fields...}}}```

Actions256

Distributors → Create suborganization

AI-generated

Overview

This node operation creates a new MSP sub-organization within the DNSFilter platform. It is useful for distributors who manage multiple sub-organizations under a main MSP account and need to programmatically add new sub-organizations. For example, a distributor can automate the creation of sub-organizations for new clients or departments within an MSP.

Use Case Examples

  1. Create a new sub-organization under an existing MSP distributor by providing the required JSON body with organization details.
  2. Automate the onboarding process of new MSP sub-organizations by integrating this node in a workflow.

Properties

Name Meaning
Body The JSON body containing the details of the sub-organization to be created. This is a required input.
Options Additional optional settings such as custom request body, headers, query filters, batching, debug mode, pagination, and timeout settings to customize the API request.

Output

JSON

  • json - The JSON response from the API after creating the sub-organization, containing details of the newly created sub-organization.

Dependencies

  • An API key credential for DNSFilter authentication is required.

Troubleshooting

  • Ensure the API key is valid and has the necessary permissions to create sub-organizations.
  • Verify the JSON body structure matches the API requirements for creating a sub-organization.
  • Check for rate limiting errors (HTTP 429) and use batching or increase batch interval to avoid hitting limits.
  • Enable debug mode to get detailed request and response information for troubleshooting.

Links

Discussion