cancel
Showing results for 
Search instead for 
Did you mean: 

Audience

Any merchant that has a setup such that all calls to Cybersource REST APIs should be routed via a cloud-based infrastructure would benefit from these new changes made to Cybersource REST SDKs.

Details

Currently, in the Cybersource REST API SDKs, a new instance of RestClient is created after each Authentication header creation call & initialized with merchantConfig.HostName.

That removes the possibility to set the baseAddress in the RestClient with values different than apitest.cybersource.com or api.cybersoure.com. There should also be a possibility to override few of the authentication headers like Host to specify custom hostname and port number of the server to which the request is being sent. That would allow to call Cybersource API via cloud-based API management platforms (e.g., Azure Api Management)

Cybersouce REST API SDK updates have been made to no longer ignore the basePath configuration sent in the constructor. Additional changes have been made to honor the custom headers set by the caller and not ignore them when SDK processes the incoming request.

What Do I Have To Do?

Use any of the Cybersource REST Client SDKs and

  • Set ApiClient.BasePath to your cloud infrastructure URL (e.g., Azure API Management URL)
  • Set any additional headers needed in Configuration.DefaultHeader collection

Which version will support this

 

rajvpate
Administrator Administrator
Administrator
2 Comments
johnsen875
Member

Great news for merchants using Cybersource REST APIs! The latest SDK updates now support routing API calls via cloud-based infrastructure, enabling customization of base addresses and authentication headers. Upgrade your SDK version to benefit from these enhancements and seamlessly integrate with platforms like Azure API Management. Stay updated with cybersource-rest-client releases to leverage these improvements effectively.

This is fantastic news—thank you for the update!

The ability to configure BasePath and honor custom headers is a significant enhancement for those of us leveraging cloud-based API management platforms like Azure API Management. This update eliminates a major limitation and brings much-needed flexibility for routing Cybersource API calls through our preferred cloud infrastructure.

The fact that it’s now possible to:

  1. Set custom BasePath for cloud-specific URLs, and
  2. Override authentication headers (e.g., Host)
    …makes the integration process smoother and more adaptable to complex setups.

For anyone planning to adopt this update, I’d suggest testing configurations thoroughly, especially with edge cases like custom ports or additional headers required by your API management platform.

Supported SDK Versions:
If you're using one of the supported versions (like cybersource-rest-client-java-0.0.52 or cybersource-rest-client-python-0.0.43), this will be a game-changer.

Thanks again for prioritizing this improvement—it’ll make Cybersource API integrations much more cloud-friendly!

Best regards,