Skip to main content
Supertab Connect SDKs handle two sides of the licensing flow: crawler operators use them to obtain license tokens for protected content, and publishers use them to verify tokens and enforce access at the edge.

SDK Availability

LanguagePackageInstallToken acquisitionVerification & enforcementCDN runtime helpers
TypeScript@getsupertab/supertab-connect-sdknpmYesYesCloudflare Workers, Fastly Compute, CloudFront
PHPgetsupertab/connect-sdk-phpComposerYesYes
Pythonsupertab-connect-sdkComing soonYesYes

Choosing the Right API

You want to…Use
Acquire a token before requesting protected contentobtainLicenseToken()
Check a token without side effectsverify()
Check a token and record usage for analytics/billingverifyAndRecord()
Protect a route or origin request end-to-endhandleRequest()
Integrate at a supported CDN edge with minimal boilerplateCDN runtime helper (cloudflareHandleRequests, fastlyHandleRequests, cloudfrontHandleRequests)
Static methods like obtainLicenseToken() and verify() can be called without initializing a client. Methods that record events or enforce access (verifyAndRecord, handleRequest, runtime helpers) require a configured client instance with your API key.

Enforcement Modes

Publisher-side request handling uses an enforcement mode to control what happens when automated traffic reaches protected content without a valid token.
ModeBehavior
SOFT (default)Requests pass through, but the SDK attaches licensing headers and records events. Use this during initial rollout.
STRICTBots without a valid token are blocked with a 401 and licensing headers.
DISABLEDNo enforcement or signaling. Requests are allowed without licensing intervention.

Language-Specific References

Each language reference covers installation, configuration, full method signatures, and code examples.

TypeScript SDK

Edge-ready SDK for Cloudflare Workers, Fastly Compute, and CloudFront Lambda@Edge.

PHP SDK

Server-side SDK for WordPress and PHP applications.