Generic REST Connector User-Agent
To watch a video explaining this, see below or click here.
We are using a Generic REST Connector successfully in SmartConnect.com.
When SmartConnect makes any call to the REST API, it passes in the generic “User-Agent” Header of “RestSharp/106.11.70.0” as the value using the name of the assembly and the version.
The 3rd-party API we’re connecting to requires us to pass in a “custom User-Agent” value, and not the generic value currently provided.
We tried adding a User-Agent header to the REST definition, but the same generic User-Agent is still being used instead of my custom value.
Is it possible to pass a custom User-Agent using SmartConnect Generic REST connector?
Previous to the March Release on 3/3/2026 for version 21.1.0.1704, the answer is no.
While not configurable, with the 21.1.0.1704 SmartConnect.com release, the Generic REST User-Agent will now be passed as:
eOne Solutions/<version>/SmartConnect
If we test the endpoint against a fake endpoint such as Beecepter or Postman Mock Server, we can see the actual call made, including the Header passed.
Now, you can see that we are sending out a customizable User Agent.
Questions on the generic REST connector User Agent in SmartConnect? Email support at support@eonesolutions.com.
