Repository navigation
Add message reactions, and thread/message create+update endpoints - #1
Merged
Merged
Conversation
Closes the gap between the SDK and the Customer API: reactions were
already live server-side but unwrapped, and thread/message creation had
no SDK surface at all (read-only until now).
- MessageResource::reactions() -> GET .../messages/{hash}/reactions/
(MessageReaction, MessageReactionUser models)
- ThreadResource::create() -> POST /threads/ (upsert by code,
optional initial message + attachments)
- ThreadResource::update() -> PUT /threads/{code}/
- MessageResource::create() -> POST /threads/{code}/messages/
Prepares CHANGELOG.md for the first tagged release, 0.1.0.
… type The OpenAPI spec lives at /docs/customer/openapi.json. The lastMessageHash cursor is inclusive and the API has no page size, so paginate_messages.php is rewritten as an incremental sync. README now documents that 402 plan limits and 403 ACTION_FORBIDDEN surface as ApiException, which API key type the SDK needs, and that response meta is not exposed.
Fix OpenAPI link, document cursor semantics, 402/403 errors and token type
Reject an empty HTTP method or URL in CurlHttpClient before calling cURL (fixes PHPStan 2.3 curl_setopt_array non-empty-string check) and date the first release in the changelog.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Audit of
htdocs/route/route.api.customer.v1.phpin the main repo against this SDK's resources found it only covered reads: no way to create a thread, update one, or send a message at all, and reactions (already live server-side) weren't wrapped either.MessageResource::reactions()→GET /threads/{code}/messages/{hash}/reactions/— newMessageReaction/MessageReactionUsermodels (hydrated from the real repository shape, not the slightly stale OpenAPI doc).ThreadResource::create(array $payload)→POST /threads/— upsert by code, optional initial message + attachments.ThreadResource::update(string $code, array $changes)→PUT /threads/{code}/.MessageResource::create(string $threadCode, array $payload)→POST /threads/{code}/messages/.All new write methods follow the existing "arrays in, typed models out" convention (same as
users()->create()).This also moves
CHANGELOG.md's[Unreleased]entries into[0.1.0] - 2026-07-17— this package has never been tagged, so 0.1.0 is proposed as the first release version. Happy to adjust before tagging.Test plan
composer test— 89 tests, 250 assertions, all greenvendor/bin/phpstan analyse(level 9) — no errorscomposer cs(php-cs-fixer dry-run) — clean