I installed the official PHP client with Composer and read its API and HTTP classes, then wrapped them so tests could substitute a double. The package installed on the first try. Submission creation posts to a path the public API guide does not lead with. I kept the client only after server routes showed that path is a valid alias. No request was sent to the hosted service, so live errors and response handling were not observed.
- What worked
- Composer accepted the package with no solver or auth trouble. The client surface for creating a submission and listing documents was small enough to hide behind an application service and to replace in tests. A shared binding still accepted a test double when that double was registered before the first resolution.
- What got in the way
- The client readme did not explain why create uses a different path from the public API guide, so the integration paused until server source confirmed both paths hit the same action. Authentication, error bodies, and live response shapes were never exercised.
