All Collections
Integration Partner Help Center
⚠️ Technical Issues
What should I do when I get “Invalid host configuration” notification in the widget?
What should I do when I get “Invalid host configuration” notification in the widget?

Resolving 'invalid host configuration': configure chain_symbol names for seamless ramp integration.

Updated over a week ago

The most common case for this issue is the swapAsset or offrampAsset parameter set with the unsupported CHAIN_SYMBOL name, ie. using ETH_ETH on demo environment, or GOERLI_ETH and SEPOLIA_ETH on production environment.

Please use proper CHAIN_SYMBOL names in your widget configurations that can be provided by our on-ramp and off-ramp asset API endpoints respectively of the environment used.

Remember

Call the API endpoint on the desired environment you’re interested in.

Example

If you wish to call our API endpoints:

- on production you need to use https://api.ramp.network/api base url;

- and on demo you need to use https://api.demo.ramp.network/api base url

extended with the endpoint name you’re interested in like /host-api/v3/assets (for on-ramp assets) resulting in an exemplary urls being created:

- https://api.ramp.network/api/host-api/v3/assets to call assets on production

- and https://api.demo.ramp.network/api/host-api/v3/assets to call assets on demo environment.

To create a proper CHAIN_SYMBOL name for your widget configuration combine strings given in the chain and symbol keys returned in the API response using _ as a word connector resulting in the CHAIN_SYMBOL name being created.

Did this answer your question?