👋 How can we help you?

Ubersmith Resolver Guide

The ubersmith integration can be used to resolve client / subscriber information during inbound processing.

Last updated on Invalid Date


The ubersmith integration can be used to resolve client / subscriber information during inbound processing. You can add it by dragging a resolver component into the inbound processing graph and choosing Ubersmith Resolver as the type.


You will then need to fill out three mandatory fields with information about your ubersmith installation. The API URL is usually the base URL of your ubersmith installation with a /api/2.0/ suffix. The user is a user with sufficient rights to read the client information from the API. You can then use the password of that user or an API token generated for this purpose (recommended). Please read the official ubersmith documentation for more information: https://docs.ubersmith.com/display/UbersmithDocumentation/Using+the+Ubersmith+API


By default the resolver will read any additional fields and custom fields into the subscriber resolver data. E.g. the name, email address, etc. Also all custom fields are included by default. If you would like to blacklist certain fields from being saved to the subscriber in AbuseHQ, you can add them to the Key Blacklist.


Connect the resolver in the graph, make sure the green/positive output leads to "AbuseHQ" and not through another resolver that would overwrite the subscriber data. In the end make sure you save the draft and set it live when you are ready.


AbuseHQ will automatically cache responses for a while so requests that concern the same IP won't be queried over and over again. This caching mechanism also considers the date of the last IP reassignment to avoid resolving the wrong client when asking for different timestamps.



Make sure the API is reachable from the external/outgoing IPs declared in our docs. Make sure you can query the API with the supplied information. Curl example:

curl -k -v https://<username>:<token>@<APIURL>?method=device.ip_lookup&ip=<exampleip>

Make sure the response contains a positive (2xx) status code and the information about the IP assignment and the client. If you get a 401 then most likely the user/token is wrong. 403 means that it doesn't have the required permissions. Any (other) error might mean the API URL is wrong. Please contact support if you are having trouble and don't understand what's going on.


Learn More

If you want to understand a little bit more about this feature, we recommend the following articles:

Did this answer your question?