Now we are in a position to post our Web form, which results in the information from the form being sent up to SalesForce through its API. Remember we haven't orchestrated in the email verification API yet. So, the bogus email makes it through fine.







At this point, we now have our service orchestration in action. The Vordel API Server has composed the two APIs together. If the response from the email verification API is a success, then we call the Salesforce API.

Let's see it in action:


Now let's take a closer look at how the response from the callout to the email verification API is used to check if the email is valid or not:


Finally, one of the most important aspects of orchestrating APIs is that you can apply SLAs (Service Level Agreements) and reporting to the APIs you are calling. This is especially important for SaaS services which you're paying for, such as Salesforce.com. Let's see how this is done with the Vordel API Server:


In this video blog, we saw application orchestration to a SaaS service via APIs, using the Vordel API Server. If you want to test this in action yourself, you can get your own free copy of the Vordel API Server from the Vordel website.