> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/developers/sdks.md).

# SDKs & tooling

PeakCommerce exposes a single, well-documented **REST API** rather than a fleet of language-specific SDKs. That means you can integrate from any language with an HTTP client today, and generate a typed client for your stack from the OpenAPI specification.

## Use the REST API directly

The Agent API is designed to be approachable by hand:

* **Predictable REST** over HTTPS, JSON in and out.
* **Action-oriented** — every response carries a `nextActions` array telling you the next legal call, so you can drive a flow without hard-coding URLs.
* **Scoped bearer-token auth** — see [Authentication](/developers/api-reference/authentication.md) and [Base URL](/developers/api-reference/base-url.md).

## Generate a typed client from OpenAPI

The full API is published as a machine-readable [**OpenAPI specification**](https://api.peakcommerce.com/api/v1/openapi.json). Load it into a generator such as openapi-generator, or into Postman or Redocly, to produce a typed client in your language — and regenerate to stay in sync as the API grows.

## Explore and test

* The interactive [API Reference](/developers/api-reference/api-reference.md) lets you browse every endpoint with its request and response shapes.
* **`GET /api/v1/manifest`** reports your tenant's live capabilities and event types — see [Discovery](/developers/api-groups/discovery.md).
* For event-driven integrations, see the [Webhooks overview](/developers/api-reference/webhooks-overview.md).

## Related

* [API Reference](/developers/api-reference/api-reference.md)
* [Changelog](/developers/changelog.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/developers/sdks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.