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 interacts with the DNSFilter API to retrieve information about invoices. Specifically, the 'Get invoice' operation fetches basic information of a specified invoice by its ID and the user's organization ID. This is useful for scenarios where users need to access detailed invoice data for billing or accounting purposes within their organization.

Use Case Examples

  1. Retrieve a specific invoice by providing the invoice ID and organization ID to view billing details.
  2. Use the node to automate invoice retrieval in financial workflows or reporting systems.

Properties

Name Meaning
Id The unique identifier of the invoice to retrieve.
Organization Id The ID of the user's organization to which the invoice belongs.
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

  • id - The ID of the invoice.
  • organization_id - The ID of the organization associated with the invoice.
  • amount - The total amount of the invoice.
  • status - The current status of the invoice.
  • due_date - The due date for the invoice payment.
  • created_at - The creation date of the invoice.
  • updated_at - The last update date of the invoice.

Dependencies

  • DNSFilter API key credential

Troubleshooting

  • Ensure the invoice ID and organization ID are correct and exist in the DNSFilter system.
  • Check that the DNSFilter API key credential is valid and has the necessary permissions.
  • If the API request fails, enable debug mode to see the actual request details and response for troubleshooting.
  • Be aware of API rate limits and use batching and interval settings to avoid hitting limits.

Links

Discussion