Download the PHP package chatbridge/php-sdk without Composer
On this page you can find all versions of the php package chatbridge/php-sdk. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download chatbridge/php-sdk
More information about chatbridge/php-sdk
Files in chatbridge/php-sdk
Package php-sdk
Short Description Framework-neutral PHP SDK for the ChatBridge backend integration API.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package php-sdk
ChatBridge PHP SDK
Small framework-neutral PHP 8.2 SDK for ChatBridge's backend integration API. It uses dedicated tenant-bound integration credentials; never provide tenant JWTs or X-ChatBridge-Gateway-Token values.
The SDK accepts HTTPS URLs and exact loopback HTTP URLs only. Applications should allow loopback HTTP only in their local environment and enforce HTTPS for production and for any unexpected environment value.
Install
Stable Packagist releases are created from semantic Git tags. Until the first tag is published, Packagist can expose only the development branch; consumers should use a tagged release for production.
Usage
Webhook verification
Verify the exact raw body before parsing or trusting tenant/account data. Persist the returned event ID with a unique constraint in the consuming application.
Signature verification does not persist replay state. The receiver must store event.id and a SHA-256 payload hash atomically: identical duplicates return success; a reused ID with a different hash is a conflict.
Laravel
The package auto-discovers ChatBridgeServiceProvider. It always binds ClientFactory; a default Client is bound only when CHATBRIDGE_BASE_URL, CHATBRIDGE_CLIENT_ID, and CHATBRIDGE_CLIENT_SECRET are all configured. Multi-agency applications should resolve encrypted credentials from an explicit local connection and use ClientFactory rather than a global client.
Publish configuration with:
The SDK retries transient transport errors and HTTP 408, 425, 429, 500, 502, 503, and 504 responses up to three attempts. Every retry keeps the method, body, and idempotency key while generating a fresh timestamp and nonce.
Subscription enforcement
Installing this MIT-licensed SDK does not grant access to the hosted ChatBridge service. Every Integration API request is bound to the integration client's ChatBridge tenant and requires an active subscription in addition to valid credentials, scopes, permitted WhatsApp accounts, quota, and rate-limit capacity.
ChatBridge returns HTTP 403 with subscription_required when the client-bound tenant is unpaid or expired. The SDK exposes this as ChatBridge\Sdk\Exceptions\SubscriptionRequiredException. Renewing the tenant subscription restores access without replacing an otherwise active integration credential.
Releases and Packagist
Releases use semantic Git tags such as v1.0.0. Packagist derives package versions from those tags, so this package deliberately does not declare a hard-coded version in composer.json.
Repository CI validates Composer metadata and runs the SDK tests for supported PHP versions. Before tagging a release, deploy any backward-compatible ChatBridge server endpoint that the SDK release requires, then update the changelog and wait for CI to pass.
Packagist synchronization is configured outside this repository because the Packagist API token must never be committed. See docs/releasing.md for the GitHub integration and manual webhook settings.
