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 creates a new enterprise connection for a specified organization using a given strategy and options. It is useful for managing enterprise authentication connections, such as setting up OIDC-based connections for organizational login. For example, an admin can create an OIDC enterprise connection with specific options and roles for their organization.

Use Case Examples

  1. Create an OIDC enterprise connection for organization ID 123 with custom options and role mappings.
  2. Set up an enterprise connection with authorized domains and a default role for user access control.

Properties

Name Meaning
Organization Id The ID of the organization for which the enterprise connection is being created.
Strategy The authentication strategy used for the enterprise connection, e.g., OIDC.
Options JSON object containing strategy-dependent options for the enterprise connection.
Additional Fields Optional additional settings such as default organization ID, display name, default role, role map, IDP type, and authorized domains.

Output

JSON

  • id - The unique identifier of the created enterprise connection.
  • organization_id - The organization ID associated with the enterprise connection.
  • strategy - The strategy used for the enterprise connection, e.g., OIDC.
  • options - The options object used to configure the enterprise connection.
  • display_name - The display name of the enterprise connection.
  • role_default - The default role assigned to users of the enterprise connection.
  • role_map - The role mapping configuration for the enterprise connection.
  • idp - The identity provider type for the enterprise connection.
  • authorized_domains - The list of authorized domains for the enterprise connection.

Dependencies

  • An API key credential for authentication with the DNSFilter API.

Troubleshooting

  • Ensure the organization ID is valid and the user has permission to create enterprise connections for that organization.
  • Verify that the strategy and options JSON are correctly formatted and valid according to the API requirements.
  • Check for network issues or API rate limits that might cause request failures.
  • If the API returns an error, review the error message for details and adjust the request parameters accordingly.

Links

Discussion