Download the PHP package matgro/dify-sdk without Composer
On this page you can find all versions of the php package matgro/dify-sdk. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 dify-sdk
Dify SDK for PHP
matgro/dify-sdk is a framework-agnostic PHP client for the standard Dify datasets and documents endpoints. It deliberately contains no Laravel configuration, queue, persistence, storage, UI, or credential management.
Supported API
- Create, list, update, and delete datasets.
- List documents in a dataset.
- Upload a document for asynchronous indexing, or update its text content.
- Read an indexing batch status.
- Delete a document.
The public client implements current documented Dify Knowledge Base endpoints. File-based document update is intentionally omitted because Dify marks that endpoint as deprecated; a future SDK release can model the current general document-update endpoint after its payload is verified.
Requirements
- PHP 7.4 or later.
- A Dify API key supplied by the consuming application through secure environment configuration.
guzzlehttp/guzzle7.
Installation
After a tagged release is registered on Packagist:
Usage
Create the SDK from configuration owned by the consuming application. Never commit an API key or internal Dify URL.
All operations return immutable DTOs. Pagination results provide items(), page(), limit(), total(), and hasMore(); dataset and document DTOs provide typed accessors such as id() and name().
Errors and retries
Remote HTTP failures are reported as Matgro\Dify\Exception\DifyApiException. Its message is sanitized and never contains the API key or remote response body. Invalid JSON responses are also converted to that exception.
The client retries only idempotent GET requests for transport failures, HTTP 429, and HTTP 5xx responses. It never automatically retries writes because a timeout after a remote write can otherwise create duplicate datasets/documents. A consuming application should reconcile the remote state before deciding whether to retry a write.
The constructor defaults to a 30-second request timeout, a 10-second connection timeout, two read retries, and a 200 ms retry delay. The final four constructor arguments configure those values.
Laravel integration
The SDK is framework-agnostic. A Laravel application should bind DifyClientInterface in its own service provider and obtain the base URL/API key from server-side configuration. File validation, private storage, queueing, audit records, and deletion consistency remain application responsibilities.
Development
Publishing maintainers checklist
- Ensure the suite and Composer validation pass.
- Commit the complete repository and push it to the public GitHub repository for
matgro/dify-sdk. - Verify the GitHub Actions PHP matrix.
- Create an immutable SemVer Git tag, beginning with
v0.1.0for the initial public API. - Register the repository in Packagist and verify installation in a clean project.
The package archive excludes development dependencies, tests, CI files, and test cache.
Security
Never commit API keys, Authorization headers, internal URLs, document contents, private dataset identifiers, or application logs. Report vulnerabilities privately to the maintainers rather than opening a public issue.
License
MIT. See LICENSE.
