Skip to main content

Spinning up this thread to discuss all things related to implementing and maintaining a Highway dynamic object.

Update: if you constructed your dynamic object to gather information relevant to an MC number (use case #1) by following the steps in our help center article titled Set up a Highway Integration with Dynamic Objects on or prior to January 24th, you’ll want to update the api endpoint that’s used in Step 3 under Use case #1: Gathering information relevant to an MC number. If you don’t make the update in your own configuration, your dynamic object will not work.

To reiterate, the api endpoint previously used to fetch info about the MC number (Fetch MC Object) is now invalid. Please update the endpoint in your build to the following: (Note: simply remove staging from the URL if you are using the production environment)

https://staging.gohighway.com/core/connect/external_api/v1/carriers?qaidentifiers_value_eq]=iDigits1]&q/identifiers_is_type_eq]=MC 


If you don't make this change, an error will be encountered as qeidentifiers_value_is_type_eq]=MC is not a valid search term identifier. It needs to be qeidentifiers_is_type_eq]=MC.

Lastly, I’ve updated our help center article to reflect this change.


thanks I made the edit and it no longer connects. This was a work around anyway that only got us to the search Mc page in Highway. 


Reply