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...}}}```

Actions328

Overview

This node operation reactivates a specified MSP sub-organization within the Distributors resource of the DNSFilter API. It is useful for distributors managing MSP sub-organizations who need to restore access or services to a previously canceled sub-organization. For example, if a sub-organization was canceled but needs to be reactivated to resume operations, this node can be used to send the reactivation request.

Use Case Examples

  1. Reactivating a canceled MSP sub-organization by providing the organization ID and optional request body parameters.
  2. Using the node to send a reactivation request with custom headers or query filters for advanced API control.

Properties

Name Meaning
Id The unique identifier of the MSP sub-organization to reactivate. This is a required numeric field.
Body The JSON body of the reactivation request. This is required and can include additional parameters for the reactivation process.
Options Additional optional settings such as custom request body, headers, query filters, batching, debug mode, pagination, and timeout settings to customize the API request behavior.

Output

JSON

  • json - The JSON response from the API after reactivating the sub-organization.
  • debug - Optional debug information including the actual URL, query parameters, headers, and body sent with the API request, useful for troubleshooting.

Dependencies

  • An API key credential for DNSFilter to authenticate requests.

Troubleshooting

  • Ensure the organization ID is valid and corresponds to a canceled sub-organization that can be reactivated.
  • Verify that the API key credential is correctly configured and has the necessary permissions to perform reactivation.
  • If the API returns rate limit errors (HTTP 429), adjust batching settings or add delays between requests.
  • Enable debug mode to get detailed request and response information for troubleshooting.

Links

Discussion