Download the PHP package tinovn/tino-sdk without Composer
On this page you can find all versions of the php package tinovn/tino-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 tino-sdk
Tino SDK
Bản tiếng Việt
Official SDKs and API contract documentation for the Tino UserAPI — the customer API behind tino.vn that manages services, domains, invoices and support tickets for a Tino account.
| 🐍 Python | sdk/python — 3.8+, zero dependencies |
| 🟩 Node.js | sdk/nodejs — 18+, ESM, TypeScript definitions, zero dependencies |
| 🐘 PHP | sdk/php — 7.4+, PSR-4, zero dependencies |
| 📖 Docs | docs/ — every endpoint with request, response and SDK call |
| 🤖 Agent skill | skills/tino-userapi — drop-in skill for Paperclip, Claude Code and Codex |
Quick start
All three expose the same surface: client.<group>.<operation>(), one group per section
of the API. See docs/api-contract/README.md for the full
list.
Why use the SDK instead of raw HTTP
The Tino UserAPI has sharp edges. The SDKs absorb them:
- Errors arrive with HTTP 200.
{"error":["unauthorized"]}comes back as a200 OK. The SDKs inspect the body and raise a typed error (TinoAuthError,TinoNotFoundError,TinoValidationError, …) instead of handing you a "successful" response. - Tokens rotate. A refresh invalidates both the old refresh token and the old
access token. The SDKs swap the pair atomically, retry the failed call once, and call
your
on_token_refreshhook so you can persist the new credentials. - Query encoding is PHP-flavoured.
filter[hide_cancelled]=1,key[]=a&key[]=b, booleans as1/0. Pass native structures; the SDK encodes them. - Pagination is zero-based going in, one-based coming out. Documented, not silently "fixed", so your code stays predictable.
- Some responses are binary. PDFs and certificates are exposed as raw bytes rather than mangled UTF-8.
Repository layout
How the contract was built
Every operation is described from three angles: the API's formal specification, the way Tino's own client calls it in production, and what the live service actually answers — with the live service as the tie-breaker.
195 operations were executed against https://api.tino.vn with a real account and their
responses captured, redacted and embedded in the documentation. The sweep covered the write endpoints too — orders, tickets, DNS records, VM power
actions, cancellations — on a sandbox account, with each step restoring what it changed.
The remainder are marked spec only: they need data the sandbox does not have, or they
end the session.
The catalog is committed, so the SDKs and the reference can be regenerated from a fresh clone without any additional input.
Regenerating
The catalog is committed, so generate-sdk.py and generate-docs.py run on a fresh
clone. build-catalog.py is only needed when a new specification export lands.
Hand-written SDK code (transport, auth, errors, client) is never touched by the generator; only the per-endpoint resource layer is generated, which is what keeps the three languages in step.
Releasing
Tagging publishes all three packages:
.github/workflows/release.yml verifies that the tag
matches the version in every package, runs all three test suites, checks that the
generated code still matches the catalog, and only then publishes. PyPI uses Trusted
Publishing, so no API token is stored; npm needs an NPM_TOKEN secret; Packagist picks
up tags through the GitHub integration once the repository has been submitted.
Status
Version 1.0.0. The catalog and both generated layers are complete; response samples cover
the 195 operations that could be exercised against a sandbox account. Contributions that add verified
samples for the remaining operations are welcome — see
tools/sanitize-samples.py for the redaction rules that
publishable samples must pass.
License
MIT — see LICENSE.
All versions of tino-sdk with dependencies
ext-curl Version *
ext-json Version *