lisa-abap-api

LISA ABAP API — using zi18n_service

ZCL_I18N_SERVICE (zi18n_service) is one ABAP HTTP service. Every action is a POST of a JSON body to {base}{path}/{action}, with a single response envelope:

{ "success": true,  "data": { … } }            // HTTP 200
{ "success": false, "error": { "code": "…", "message": "…" } }   // HTTP 400

Default path /sap/bc/http/sap/zi18n_service. Actions: capabilities, list_languages, list_texts, get_translation, set_translation, compare_translations. Full request/response shapes, selectors and error codes are in reference.md; the machine-readable contract is api/zi18n_service.openapi.yaml.

Authentication is out of scope — on purpose

This skill never handles a credential. Something else carries the auth, and the agent only ever sends a JSON body:

• From a BTP runtime (Joule Studio action, CAP, SAP Build): a BTP destination authenticates the call — bind your action to it. Creating that destination (per-user propagation or a shared Basic-auth user, per landscape) is documented in BTP destination setup.
• Want a runtime that holds credentials and exposes the three tools directly? Run the LISA MCP server (@lisa-mcp/server) or the ARC-1 extension — the agent calls the tools and never sees a secret.

Never build a curl -u user:pass, read a credential from a .env, or put a secret in a prompt. If you have no authenticated way to reach the system, stop and point the user at the two options above — do not improvise auth.

Workflow (pure JSON, whatever the runtime)

1. Probe first — capabilities (body {}) returns the per-action allow-list of target_types for THIS system; public cloud and on-premise support different sets. Never assume a type works (an unlisted one fails with CLOUD_UNSUPPORTED or an XCO error).
2. Read before writing — list_texts returns every slot with a populated flag (false = still to translate): {"target_type":"data_element","object_name":"ZMY_DTEL","language":"FR"}
3. Write with a transport — set_translation needs a modifiable transport request the caller's user can record into: {"target_type":"data_element","object_name":"ZMY_DTEL","language":"FR","transport":"A4HK900123","texts":[{"attribute":"short_field_label","value":"Client"}]}