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 (Managed Service Provider) parent organization and optionally its sub-organizations within the Distributors resource of the DNSFilter API. It is useful for scenarios where an MSP organization that was previously canceled or deactivated needs to be reactivated to resume its services and operations. For example, a distributor can use this operation to restore access and functionality for an MSP that had been temporarily suspended.

Use Case Examples

  1. Reactivating an MSP organization by providing its MSP ID and optional request body parameters to specify reactivation details.
  2. Using the operation to reactivate all sub-organizations under a given MSP parent organization.

Properties

Name Meaning
Id The MSP ID to identify which MSP parent organization to reactivate. This is a required numeric identifier.
Body The JSON body containing additional parameters or data required for the reactivation request. This is required and allows customization of the reactivation process.
Options Additional optional settings for the request such as custom headers, query filters, batching, debug mode, pagination, and timeout settings to control the API call behavior.

Output

JSON

  • json - The JSON response from the API call, containing the result of the MSP reactivation operation.

Dependencies

  • An API key credential for DNSFilter API authentication.

Troubleshooting

  • Ensure the MSP ID provided is valid and corresponds to an existing MSP organization.
  • Verify that the API key credential used has sufficient permissions to perform reactivation operations.
  • Check for network connectivity issues or API rate limiting indicated by HTTP 429 responses.
  • If debug mode is enabled, review the detailed request and response information included in the output to diagnose issues.

Links

Discussion