Assembly Editor
Other Assembly Types
Web Services
5 min
web services are assemblies that can be invoked via a url it is also possible to build web service automations with the automation editor see web service docid\ s9mlctdr3xgoagyxualka web services make it possible to build rest style api endpoints in the form of assembly diagrams that can be invoked and return data to other systems and programming tools all web service assemblies must have a web service output module that emits data three versions of the web service output module are currently available xml, json, and csv input into web services can be received as either one or more query parameters on the url that are received by query parameter modules, and/or as a post payload received with the post body module in this example, the web service accepts one query parameter named "tags" that will search flickr for photos having the matching tags when the execute assembly link at the top right of the editor is clicked for web services, an option will appear to run the web service in a new browser tab this can be used to obtain the url for invoking the web service the above example flickr web service can accept a "tags" query parameter, so let's add that to the url to filter the results when an assembly containing a web service output module is saved, a system wide unique web service name must be entered this unique name can be used to invoke the web service instead of using the assembly uuid query parameter web services are easily consumed within other assemblies in apiant by dragging web services out of the catalog notice that the "tags" query parameter is an available input value in the web service module query parameter and post body modules can only be placed in the top level web service assembly, not within subassemblies the web service may use managing web services select this menu option under the more menu at the top right to manage your web services a dialog will open listing all your web services accounts having a subscription plan will be able to see how many times their web services have been invoked for the current billing period