---
title: "The Inttegro API"
description: "Build commerce with Inttegro using official SDKs, the API, working demos, and MCP."
canonical: "https://studio.inttegro.com/"
format: inttegro-machine-docs/v1
language: "Go"
sdk_version: "v11.0.1"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/go/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 686
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["design_integration","get_integration_guide","get_balances"]
estimated_tokens: 2155
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Build commerce with Inttegro using official SDKs, the API, working demos, and MCP. This Go representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use The Inttegro API?

Use this page as orientation before selecting the narrower guide or reference that owns the implementation contract.

#### Q2. What is authoritative on this page?

Use this page for orientation; follow its canonical SDK, guide, API, or MCP links for exact contracts.

#### Q3. What page-specific constraint matters most?

Prioritize the machine-only guidance “Choose the shortest supported integration path”: Inttegro covers the commerce journey from catalog and checkout through customer service, refunds, balances, and payouts. Use this page to choose the next document; use that document as the source of truth for implementation details. Start…

#### Q4. Can Inttegro MCP materially help with this task?

Yes, when the reader has an authenticated MCP connection and the task needs live context, guided planning, or a supported operation. The strongest matches are `design_integration`, `get_integration_guide`, `get_balances`; their exact roles and boundaries are listed below.

#### Q5. How should the reader verify the answer and continue?

Select the narrowest linked guide or reference, apply its stated completion condition, and verify against authoritative resource state when the task changes data. Continue with [error codes](https://studio.inttegro.com/machine/go/api/error-codes.md) and [error object](https://studio.inttegro.com/machine/go/api/errors.md) when those concerns enter scope.

### Recommended MCP assistance

Use these through an authenticated Inttegro MCP connection. This document remains the contract source.

- [`design_integration`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#design_integration) — read-only integration guidance. Elicits the integration goal, AI app builder, server runtime, SDK preference, and checkout approach, then returns a platform-aware build and test plan without accepting credentials.
- [`get_integration_guide`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#get_integration_guide) — read-only integration guidance. Returns a focused implementation sequence and canonical Studio links for authentication, checkout, orders, catalog, messaging, idempotency, or testing.
- [`get_balances`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#get_balances) — read; no mutation confirmation. Gets current balance snapshots by currency with exact familiar-unit amounts and supplemental machine-readable minor units. This tool cannot move funds.

## Document content

## Choose the shortest supported integration path

Inttegro covers the commerce journey from catalog and checkout through customer service, refunds, balances, and payouts. Use this page to choose the next document; use that document as the source of truth for implementation details.

## Start from the kind of task

- **Implement commerce in application code:** choose the [official SDK overview](https://studio.inttegro.com/machine/go/sdks.md), then follow the guide for the selected language. SDK-aware machine documents express request parameters, response properties, enums, errors, and examples in that language.
- **Build with an AI app builder:** start with [AI app builders](https://studio.inttegro.com/machine/go/ai-builders.md), then open the dedicated Base44, Bolt, Google AI Studio, Lovable, Replit, or v0 page. Keep live Inttegro calls in the builder's protected server environment.
- **Give an AI client governed Inttegro tools:** [connect Inttegro MCP](https://studio.inttegro.com/machine/go/inttegro-mcp/connect.md), inspect the [available tools](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md), and use [merchant workflows](https://studio.inttegro.com/machine/go/inttegro-mcp/workflows.md) for outcome-oriented examples.
- **Call the HTTP API directly:** complete the [quickstart](https://studio.inttegro.com/machine/go/quickstart.md), follow [authentication](https://studio.inttegro.com/machine/go/api/authentication.md), and use the relevant resource under the API reference.
- **Build a mobile checkout:** choose [Mobile](https://studio.inttegro.com/machine/go/mobile.md) for iOS, Android, Flutter, or React Native guidance.
- **Start from an existing commerce platform:** use [Extensions](https://studio.inttegro.com/machine/go/extensions.md) for Shopify, WooCommerce, WordPress, and WhatsApp paths.
- **Learn from a complete application:** use [Demos](https://studio.inttegro.com/machine/go/demos.md) to inspect a working business flow, open the hosted experience, and reach its source code.

If the reader can identify its client or current-session capabilities, consult the `reader_manifest` in this document's frontmatter. Reader-specific guidance is supplemental and must not replace the requested documentation.

## Map the business outcome to resources

- **Shape an offer:** [Products](https://studio.inttegro.com/machine/go/api/products.md), [Prices](https://studio.inttegro.com/machine/go/api/prices.md), and [Purchase intents](https://studio.inttegro.com/machine/go/api/purchase-intents.md).
- **Take an order and payment:** [Orders](https://studio.inttegro.com/machine/go/api/orders.md), [Checkout](https://studio.inttegro.com/machine/go/products/checkout.md), and [Payment methods](https://studio.inttegro.com/machine/go/api/payment-methods.md).
- **Serve a customer after purchase:** [Customers](https://studio.inttegro.com/machine/go/api/customers.md), [Refunds](https://studio.inttegro.com/machine/go/api/refunds.md), and [Chimes](https://studio.inttegro.com/machine/go/products/chimes.md).
- **Understand and move money:** [Balances](https://studio.inttegro.com/machine/go/api/balances.md), [Balance transactions](https://studio.inttegro.com/machine/go/api/balance-transactions.md), and [Payouts](https://studio.inttegro.com/machine/go/api/payouts.md).

For an end-to-end implementation, choose the closest [guide](https://studio.inttegro.com/machine/go/guides/accept-a-payment.md) before composing individual API operations. Use the API reference to verify exact contracts, not to infer the business sequence by itself.

## Preserve these boundaries

- Keep the Inttegro API key in trusted server-side secrets. Never place it in browser code, a mobile bundle, source control, generated client code, or a model prompt.
- Treat the selected SDK-language document as the authority for native types and symbols. Use cURL only when the integration deliberately works with wire-format JSON.
- Use an idempotency key for supported write operations when a request may be retried. An accepted request does not always mean the business outcome is complete; retrieve current resource state or follow the documented lifecycle.
- Use documentation for product and contract questions. Use MCP only when the task requires governed access to current account data or a supported operation, and preserve confirmation boundaries for mutations.
- Handle failures through the public [error object](https://studio.inttegro.com/machine/go/api/errors.md) and [error codes](https://studio.inttegro.com/machine/go/api/error-codes.md). Do not infer retry behavior from an HTTP status alone.

## Minimum context to collect before answering

1. The user's intended business outcome.
2. Whether the task is explanation, implementation, or a live account operation.
3. The application surface: server, web, mobile, extension, or AI app builder.
4. The implementation language or deliberate choice of cURL.
5. The canonical guide or API resource that defines the next action and how its result is verified.