An API gives mobile apps and partners a stable 1C contract without exposing configuration internals. I design HTTP services and, when needed, an intermediary facade with versions, authorisation, and conventional JSON.

Scope includes resources, externalId, validation, idempotent commands, rate limits, OpenAPI, and request logs without secrets. Acceptance tests documentation from a clean client, repeats, denied roles, old versions, and 1C outages. Errors provide a safe log correlation code, and contract changes remain compatible or receive a new version.