Download the PHP package pritset/pritset-php without Composer

Pritset PHP SDK

Official PHP client for managing Pritset DOCX templates and generating PDFs.

Version 0.1.5 targets Pritset SDK contract 1.0.0.

Requirements

• PHP 8.3 or newer
• Composer 2
• A Pritset access token and secret

Installation

Install version 0.1.5 from Packagist:

For SDK development from a source checkout, add this repository as a Composer path repository.

Create a client

Pritset expects the access token directly in the Authorization header—do not add a Bearer prefix. Credentials are kept private and redacted from normal object debug output. Never commit them or include them in logs.

Generate a PDF

generate() returns a streaming response, so large documents do not need to be buffered in memory.

The underlying PSR-7 stream is also available as $pdf->stream. getContents() and saveToFile() consume from the stream's current position.

Templates

List and inspect

Create and update

Uploads can come from a path, a string, a PHP resource, or a PSR-7 stream:

Download and delete

Validate a template

Template validation uses the same token-and-secret authentication as the other public template operations and is supported by contract 1.0.0.

Webhook generation

Webhook URLs must be absolute HTTP(S) URLs and cannot contain embedded credentials. The SDK sends the URL to Pritset; it does not call the webhook itself.

Raw JSON

Document data may be an array, JsonSerializable object, or already encoded JSON string. Raw strings are validated before a request is sent.

Errors

Transport exceptions intentionally do not retain the original Guzzle exception because it can hold credential-bearing request headers.

Configuration and custom HTTP clients

The injected client implements Guzzle's ClientInterface, which is compatible with PSR-18 request semantics while supporting the multipart and streaming options used by this SDK. Redirects are always disabled to prevent credentials from being forwarded to another origin. HTTPS is required except for explicit localhost, 127.0.0.1, or ::1 development endpoints.

Compatibility

Pre-1.0 releases may contain API changes between minor versions. Pin an exact minor version in production and review the changelog before upgrading.

Development

The contract hash check, PHPUnit suite, and PHPStan level 8 analysis all run in CI on PHP 8.3, 8.4, and 8.5.

Production test-user lifecycle validation

The opt-in production test validates template upload, listing, details, update, download, direct PDF generation, webhook job submission, deletion, and the final 404 response. It must use a dedicated production test user. The test creates a uniquely named template and removes it in a finally cleanup block. A short configurable delay lets the asynchronous webhook job start before cleanup; this test confirms submission, not delivery to the receiver.

For a local PowerShell run, copy .env.example to .env, fill in the dedicated production test-user credentials and controlled webhook URL, and set both production confirmation flags to true. The .env file is ignored by Git. Then run:

To use a file in another location:

The launcher requires typing RUN-PRODUCTION-TEST before it contacts production. It reads only known Pritset settings, never prints secret values, restores the previous process environment afterward, and requires the raw Pritset access token without a Bearer prefix.

The launcher requires installed Composer dependencies but invokes PHP directly. It selects a readable CA certificate bundle from PRITSET_CA_BUNDLE_PATH, PHP configuration, or Git for Windows and passes it only to the lifecycle process. This avoids changing the machine-wide PHP configuration.

The manual Production test lifecycle GitHub Actions workflow uses the protected production-test environment and requires the same confirmation. Configure PRITSET_ACCESS_TOKEN, PRITSET_SECRET, and PRITSET_WEBHOOK_URL as environment secrets and PRITSET_PRODUCTION_TEST_USER_CONFIRMED=true as an environment variable. Add required reviewers and restrict deployment branches before running it.

The lifecycle may consume production test-user credit and create webhook traffic. A 401 on the first validation request means the credentials were rejected; no template has been created at that point.

License

MIT © Pritset. See LICENSE.