Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

How to Read in REST Parameters in the Axway Vordel API Server

DZone's Guide to

How to Read in REST Parameters in the Axway Vordel API Server

· Integration Zone
Free Resource

Modernize your application architectures with microservices and APIs with best practices from this free virtual summit series. Brought to you in partnership with CA Technologies.

The Axway Vordel API Server allows you to read in REST API parameters from an incoming request, and then use these parameters for a variety of purposes, for example to pass them into a SOAP message, or use them to call a method of a Java class via the Scripting Filter. 

The key to this is the "Extract REST Request Attributes" filter. If I type in "REST" into the search box on Policy Studio, it helpfully narrows down the filter list to just the filters related to REST.


When I drag in an "Extract REST Request Attributes" filter, I see this configuration below. As you can see, you can have the API Server read API parameters from the querystring or from HTTP POST parameters.


Once I place this filter into a policy which is mapped to a REST endpoint on the API Server (e.g. a relative path), I can then access the REST parameters in other filters. 
Let's say a parameter is passed like this:
I can now access the content of the "customerID" parameter like this:
 ${http.querystring.customerID}

The Integration Zone is proudly sponsored by CA Technologies. Learn from expert microservices and API presentations at the Modernizing Application Architectures Virtual Summit Series.

Topics:

Published at DZone with permission of Mark O'Neill, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}