LegnaSend
Developer docs简体中文

LEGNASEND / DEVELOPERS

Developer & API documentation

From enabling the service to writing a client: endpoints, authentication, fields, examples, limits, errors and troubleshooting. These are the LegnaSend client’s open API manuals. The PHP download portal neither proxies nor executes these endpoints.

Endpoints & calling examples

Status, workspaces, files, uploads, send tasks, settings and audit, with cURL, JavaScript and Python.

Authentication & permissions

Bearer keys, TLS/CORS, one-time secrets, lifecycle, scopes and replay rules.

Parameters, rates & errors

Field budgets in the limits guide; request rates, concurrency, 429 and error codes in the integration reference.

Debugging & recovery

In-app explorer, request history, retention, resume and cleanup evidence; implementation and device acceptance remain distinct.

Quick start

  1. Enable the service in the app API page, choose permissions/workspaces and create a key.
  2. Use the actual listener protocol, address and port shown in the app. HTTPS requires device certificate trust and, where applicable, a client certificate.
  3. Call /status and /capabilities with the Bearer key, then read workspaces and their generation.
  4. Act within advertised capabilities and permissions. Keep request IDs; distinguish throttling, stale generations and unknown outcomes before retrying mutations.
shell
curl "$BASE/api/legnasend/v1/integration/status" \
  -H "Authorization: Bearer $TOKEN"

curl "$BASE/api/legnasend/v1/integration/capabilities" \
  -H "Authorization: Bearer $TOKEN"

BASE is the actual LegnaSend client service address (scheme, HOST and PORT), not the portal domain; TOKEN is a key created in the app. No runtime credentials are bundled.

Download OpenAPI

English · OpenAPI 3.1简体中文 · OpenAPI 3.1繁體中文 · OpenAPI 3.1香港繁體 · OpenAPI 3.1

Static snapshots describe authentication-required mode. Live capabilities and anonymous policy depend on the running service.

Troubleshooting order

Check the actual listener and TLS trust first, then API enablement, key status/scopes and workspace generation. Use the in-app request console for status codes and request IDs. Back off on 429 and follow each endpoint’s conflict, cancellation and unknown-outcome rules. Keep keys, passwords and file bodies out of logs.

Full error contract and examples