​
Ubersmith Setup

The Ubersmith integration allows AbuseHQ to resolve client/subscriber information during Inbound Processing.
You can configure it by adding a Resolver to the Inbound Processing graph and selecting Ubersmith Resolver as the type.

​
Accessing the Ubersmith Resolver Setup

To configure the Ubersmith Resolver:
  1. Open the Admin Portal.
  2. Click Settings in the left menu under AbuseHQ.
  3. Click Inbound Processing under Automation.
  4. Drag a Resolver node into the graph and set the Type to Ubersmith Resolver.

​
Required Fields

You will need to fill out the following mandatory fields:
  • API URL – Usually your Ubersmith base URL with the /api/2.0/ suffix
    Example: https://your-ubersmith-instance.com/api/2.0/
  • Username – An account with permission to read client information
  • Password or API Token – Preferably an API token generated for this integration
📚 For more info, consult the Ubersmith API documentation

​
Optional Configuration: Key Blacklist

By default, the resolver will:
  • Read and import standard fields like name, email, etc.
  • Include all custom fields
To exclude specific fields from being saved in the subscriber data in AbuseHQ, add them to the Key Blacklist.

​
Graph Connection

  • Connect the positive (green) output from the resolver directly to “AbuseHQ”
  • Avoid chaining it through another resolver that could overwrite subscriber data
  • After setup, save your draft and click “Set it Live” when ready

​
Caching Behavior

AbuseHQ automatically caches resolver responses:
  • Prevents repeated queries for the same IP
  • Considers the timestamp and IP reassignment to avoid returning outdated subscriber info

​
Troubleshooting

​
✅ Check API Connectivity

Ensure your API is accessible from Abusix’s outbound IPs:
  • 18.193.183.51
  • 52.57.46.129
  • 18.158.191.233

​
🔍 Test with curl

Use the following example command to verify your Ubersmith API setup: 
curl -k -v "https://<username>:<token>@<APIURL>?method=device.ip_lookup&ip=<exampleip>"
Ensure the response contains a positive (2xx) status code and information about the IP assignment and the client. If you get a 401, the user/token is most likely 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 happening.