- If you are using this API for commercial purposes be aware that it is not provided for that purpose. Availability and uptime may not meet your commercial needs. SPOT has a purchasable commercial product for this express purpose. Please contact me at the above email if you wish to know more about it.
- RC4 has been disabled
- SSLv3 has been disabled.
If you are suddenly having issues, it is a good bet that your SSL library is old. Update that and things will probably start to work again. If not, email me at the above email and I will do my best to help you.
Be considerate when making API calls, this service is provided free of charge, please do not abuse it. Repeatedly accessing the same feed in very short time periods will result in your IP being blocked or your feed disabled.
If you start receiving a 403 error when you attempt to access your feed it is because you are polling much too quickly and you will need to email firstname.lastname@example.org in order to get your feed reinstated. Please allow as least 2.5 minutes between calls of the same feed and if you are pulling multiple feeds have your application sleep at least 2 seconds between feed requests.
-- The API will only return data from the point in time the feed was created, up to a maximum of 7 days. Example: If you create a brand new feed for a device today, you will not be able to pull data from previous days on this new feed. --
The SPOT shared page is built upon an XML data stream that is enabled when a new shared page is created.
The first step is to create a Share Page in your account. Once you have the Shared Page created, you can then obtain your FEED_ID from the URL of the Shared Page.
The glId in the following url is the FEED_ID you will need below. (Please note the glId/FEED_ID in the examples below is non-functional, it is for example purposes only)
The XML document will contain 0 or more messages. Only the messengers and message types enabled by the customer will be available in this data stream. In addition, viewing limits are imposed on all shared page links and abuse of this feature may cause the viewing limits to come into effect.