In scenarios where latency is a concern, a proxyless approach can be used.
For information about our standard proxy-based solution click here.
For a complete technical description of how to implement the proxyless API management solution, click here.
API Users will sign up and receive an API key through the WebServius UI. The key will contain features that will allow a fake key to be quickly rejected by the API provider without calling WebServius.
API User's application will make a call directly to the API provider which will contain the API key. The exact format of how the API key will be included in the call is up to the API Provider's discretion.
The API Provider will authorize or deny the call at its discretion. It will typically use the Authorize call and/or cached authorization data to make that decision.
The Authorize call lets an API Provider verify whether a particular API key is valid and has sufficient balance left.
The Charge call lets an API Provider charge API Users for usage. It is not necessary to call Authorize prior to calling Charge.
Copyright © WebServius 2008-2013