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.
To configure the Ubersmith Resolver:
Ubersmith Resolver
.You will need to fill out the following mandatory fields:
/api/2.0/
suffixhttps://your-ubersmith-instance.com/api/2.0/
📚 For more info, consult the Ubersmith API documentation
By default, the resolver will:
To exclude specific fields from being saved in the subscriber data in AbuseHQ, add them to the Key Blacklist.
AbuseHQ automatically caches resolver responses:
Ensure your API is accessible from Abusix’s outbound IPs:
curl
Use the following example command to verify your Ubersmith API setup:
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.
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.
To configure the Ubersmith Resolver:
Ubersmith Resolver
.You will need to fill out the following mandatory fields:
/api/2.0/
suffixhttps://your-ubersmith-instance.com/api/2.0/
📚 For more info, consult the Ubersmith API documentation
By default, the resolver will:
To exclude specific fields from being saved in the subscriber data in AbuseHQ, add them to the Key Blacklist.
AbuseHQ automatically caches resolver responses:
Ensure your API is accessible from Abusix’s outbound IPs:
curl
Use the following example command to verify your Ubersmith API setup:
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.