Service registration and terms
Most TMS FNC Cloud Pack components call hosted services, so applications normally need provider registration before the component can authenticate or execute requests.
Register an application
Register the application with the cloud provider and record the credentials required by the component. OAuth-based services usually require a client ID, client secret, and callback URL. API-key services usually require a single key or service token.
Use the TMS service key guide to find the provider-specific registration route:
After registering, set the credentials on the component's Authentication object, call Connect for OAuth services, and wait for the connected event before calling service operations. API-key services can usually execute requests once the key has been assigned.
Terms of use
With TMS FNC Cloud Pack you receive source code and support for integrating supported cloud services in Delphi applications. The application owner is still bound by the third-party provider's terms, quotas, service availability, and billing rules.
| Provider family | Terms |
|---|---|
| Google services | Google APIs terms |
| Microsoft services | Microsoft APIs terms of use |
| Dropbox | Dropbox terms |
| YouTube | YouTube terms |
| PayPal | PayPal legal agreements |
| Hubic | Hubic contract |
| Stellar Data Store | StellarDS terms |
The application owner is responsible for complying with the selected provider's terms and for paying any provider fees that apply to the application's usage.
Limited warranty
TMS Software cannot guarantee the current or future operation, approval, availability, terms, quotas, or uptime of third-party cloud services. If a provider changes its conditions, service availability, or API behavior, TMS Software will make reasonable efforts to accommodate the change where technically possible, but provider changes remain outside TMS Software's control.