Introduction to the Highwinds APIs
API Example JSON and RESTful Endpoints Account Context Authentication X-Application-Id Header The Highwinds APIs completely expose the full Highwinds CDN configuration system to users for tw...
Read ArticleAPIs
Quick Start Guide to APIs
StrikeTracker is built right on top of Highwinds APIs. If you already have access to a user profile and know the account hash for the account you’d like to make changes to, all you need is an access token and y...
Read ArticleHighwinds Interactive API Documentation
The Highwinds Interactive API Documentation, accessible from within your StrikeTracker account, is an excellent resource that can help you write your own API requests by demonstrating to you how Highwinds API r...
Read ArticlePurge via API
Note: StrikeTracker has a rate limit on purge calls via API. To learn more, read about StrikeTracker's API purge call rate limit. In order to purge a file named index.html from the cdn.example.com host first p...
Read ArticleReference
Overview Pops Docs Version BillingRegions Configuration Overview Reference resources are those for which the only changes occur due to expansions in capacity or capabilities brought about ...
Read ArticleHighwinds Cloud Storage specific API documentation
API Quick Reference Create a Container Delete a Container List All Containers in Account Container Permissions Write Access Read-Only Access List All Objects in a Container Upload an Objec...
Read ArticleLegacy API Documentation: StrikeTracker 2 to StrikeTracker 3
The purpose of this document is to aid you in the conversion of code that uses previous StrikeTracker APIs to use the new StrikeTracker API. The new API gives you much more flexibility, improved security, and ...
Read ArticleRate limiting policy of StrikeTracker's API Purge Calls
Highwinds customers can use API endpoints for purging the cache for their sites. To ensure operational efficiency for all customers, Highwinds limits the number of API purge requests to 100 URI’s per account ev...
Read Article