> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/seb-docs-draft/seb-docs-public-lv/integracija/api-klienta-sdk/celvezi.md).

# Ceļveži

Starpvalodu norādījumi drošām, uzticamām un paplašināmām SDK integrācijām.

Starpvalodu tēmas, kas attiecas uz visiem četriem SDK. Lasiet tās kopā ar ātro darba sākšanu un integrācijas rokasgrāmatu savā valodā.

* [Kļūdu apstrāde](/seb-docs-draft/seb-docs-public-lv/integracija/api-klienta-sdk/celvezi/kludu-apstrade.md) — `ECommException` hierarhija, API kļūdu nolasīšana un ko SDK politika bez atkārtotiem mēģinājumiem nozīmē izsaukumiem, kas maina stāvokli.
* [Drošības mehānismi](/seb-docs-draft/seb-docs-public-lv/integracija/api-klienta-sdk/celvezi/drosibas-mehanismi.md) — OAuth 2.0 autentifikācija, JWE maksājumu kartes datu šifrēšana, tīmekļa āķa paziņojumu autentiskuma pārbaude un droša reģistrēšana žurnālā.
* [Arhitektūra un paplašināmība](/seb-docs-draft/seb-docs-public-lv/integracija/api-klienta-sdk/celvezi/arhitektura-un-paplasinamiba.md) — heksagonālais (porti un adapteri) dizains: pieci porti, to noklusējuma adapteri un kāpēc SDK ir veidots šādi.
* [SDK adapteru pārrakstīšana](/seb-docs-draft/seb-docs-public-lv/integracija/api-klienta-sdk/celvezi/sdk-adapteru-aizstasana.md) — katrā valodā nomainiet iebūvēto HTTP klientu, reģistrētāju, serializētāju vai šifrētāju pret savu.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ecommerce.seb.ee/seb-docs-draft/seb-docs-public-lv/integracija/api-klienta-sdk/celvezi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.