Authentication
Our users store valuable information in Coolfront Mobile, so we take strong measures to protect their data. Applications that wish to connect to Coolfront Mobile via Fizz must connect using SSL and provide valid credentials in order to access a company's data -- SSL is not currently supported in the sandbox. These credentials are "handed out" by Coolfront Mobile users at their discretion.
You see, all of my most secret inventions are cooking and simmering in here. Old Slugworth would give his false teeth to get inside for just five minutes, so don't touch a thing!
Enabling Fizz
A Coolfront Mobile user provides you with credentials by enabling Fizz for their organization. In other words, they grant you access to their instance and data. The process is simple. If you have a user who wishes to integrate Coolfront Mobile with your software, have them:
- Contact Profit Strategies and complete an API approval request.
- Send you the resulting security token.
Security Tokens
Security tokens are required for ALL calls made to Coolfront Mobile via Fizz. No token, no touchy! Once a token is generated by a user, that token will remain in effect for the life of their subscription ("Everybody has had one and one is enough for anybody"). Tokens are GUIDs generated by the Coolfront Mobile system. These 128 bit identifiers follow the common hexidecimal notation: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
Example: 3F2504E0-4F89-11D3-9A0C-0305E82C3301
See Pushing Data and Pulling Data for specifics on how to use security tokens to authenticate to Coolfront Mobile.
All quotes attributed to Willy Wonka, the sweetest of men.
- Home
- Overview
- Workflow
- Authentication
- Pulling Data
- Pushing Data
- API Reference
- Getting Support
- ChangeLog