API v4.0 is now available. The updated API and all five official SDKs are live and ready to use.
New SDKs
Five official SDKs are available for API v4.0, replacing the legacy RBLTracker SDKs for PHP, Node.js, and Python. Go and Ruby are new additions.
| Language | Install | Repository |
|---|---|---|
| PHP | composer require generatorlabs/sdk |
github.com/generator-labs/php-sdk |
| Node.js | npm install generatorlabs |
github.com/generator-labs/node-sdk |
| Python | pip install generatorlabs |
github.com/generator-labs/python-sdk |
| Go | go get github.com/generator-labs/go-sdk |
github.com/generator-labs/go-sdk |
| Ruby | gem install generatorlabs |
github.com/generator-labs/ruby-sdk |
What's New in v4.0
Certificate Monitoring API. All five SDKs include full support for the Certificate Monitoring API: listing certificate errors, managing certificate monitors, and managing certificate profiles. This was not available in the v3 API.
Expanded language support. Go and Ruby SDKs are new. The existing PHP, Node.js, and Python SDKs have been rebuilt under the Generator Labs package name with updated language requirements: PHP 8.1+, Node.js 18+, Python 3.8+.
TypeScript. The Node.js SDK is now written in TypeScript with full type definitions included.
Automatic pagination. All SDKs handle paginated responses automatically. Iterate through large result sets without manual page management.
Retry logic. Automatic retry with exponential backoff is built into all SDKs. The Retry-After header is respected when the API returns rate limit responses.
Webhook verification. All SDKs include a helper for verifying the HMAC signature on incoming webhook requests.
Migrating from v3
If you are using the legacy v3 packages, migrate to the new packages above. The v3 packages remain available but will not receive updates.
- PHP: github.com/rbltracker/rbltracker-php (
composer require rbltracker/sdk) - Node.js: github.com/rbltracker/rbltracker-node (
npm install rbltracker) - Python: github.com/rbltracker/rbltracker-python (
pip install rbltracker)
The v4.0 API uses the same Account SID and Auth Token credentials. The base URL and authentication scheme are unchanged. Refer to the API documentation for the full endpoint reference and the migration guide for step-by-step migration notes.