---
title: "WordPress extension"
description: "Put an Inttegro catalog and secure Buy buttons on your WordPress site."
canonical: "https://studio.inttegro.com/extensions/wordpress"
format: inttegro-machine-docs/v1
language: "Ruby"
sdk_version: "v10.0.0"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/ruby/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: 343
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 1455
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Put an Inttegro catalog and secure Buy buttons on your WordPress site. This Ruby representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use WordPress extension?

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?

Use the page to choose a canonical next source instead of treating summary material as a complete implementation contract.

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

No catalog ability is sufficiently specific to recommend for this page. Use the documentation directly; consult the MCP catalog only if the task later requires governed live account context or a supported operation.

#### 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 [Need WooCommerce?](https://studio.inttegro.com/machine/ruby/extensions/woocommerce.md) when those concerns enter scope.

## Document content

![WordPress](/img/logos/extensions/wordpress.svg)

# Start selling from WordPress

Add your Inttegro products to any WordPress page and send a customer to checkout
when they select **Buy**. Most installations take only a plugin upload, an API
key, and one catalog block. [Download the WordPress ZIP](https://github.com/inttegro/inttegro-extensions/releases/download/v1.1.0/inttegro-wordpress-1.1.0.zip) [Need WooCommerce?](https://studio.inttegro.com/machine/ruby/extensions/woocommerce.md) |              |                                        |
| ------------ | -------------------------------------- |
| Version      | 1.1.0                                  |
| Requirements | WordPress 6.5–7.1 and PHP 8.1 or newer |
| Availability | Ghana pilot                            |

## Before you install

You need an Inttegro account with at least one active product and price, access
to install WordPress plugins, and a dedicated server-side API key. The key is
intended to allow only `products:read` and `purchase_intents:create`.

:::warning API-key scopes are not enforced yet

Use a key created only for this site. Do not reuse a key that can access payouts,
financial accounts, product writes, or account administration. Rotate it when
restricted keys become available.

:::

## Connect WordPress

### 1. Install the plugin

[Download `inttegro-wordpress-1.1.0.zip`](https://github.com/inttegro/inttegro-extensions/releases/download/v1.1.0/inttegro-wordpress-1.1.0.zip),
then open **Plugins → Add New Plugin → Upload Plugin** in WordPress. Choose the
ZIP, select **Install Now**, and activate **Inttegro**.

### 2. Connect the site

Add `INTTEGRO_API_KEY` to `wp-config.php`. If your host cannot manage server
secrets, open **Settings → Inttegro**, enter the API key, save, and select
**Test connection**.

Do not leave the API key in the field after it has been saved. A successful
test confirms that WordPress can read your Inttegro catalog.

### 3. Add the catalog

Edit the page where you want to sell, add the **Inttegro catalog** block, and
publish the page.

The catalog block is server-rendered. Customers receive product data and Buy
links, never your API key.

Prefer the classic editor? Add the shortcode instead:

```text
[inttegro_catalog page_size="12" columns="3"]
```

### 4. Open the published page

Confirm that the catalog loads and select **Buy** on a low-value test product.

## Verify the setup

- \[ ] The published page shows the same active products and prices as Inttegro.
- \[ ] Selecting **Buy** opens an Inttegro Checkout URL.
- \[ ] Changing a product in Inttegro appears in WordPress after the catalog
  cache refreshes.
- \[ ] `INTTEGRO_API_KEY` is absent from page source and browser network requests.

Once these checks pass, the page is ready to share. WordPress will keep reading
the catalog from Inttegro, while checkout collects the information needed to
complete each purchase.

:::note Why the plugin creates a purchase intent

The standalone plugin does not create Inttegro orders or send WordPress visitor
details to Inttegro. It sends only the selected product ID, price ID, and
quantity, then redirects to checkout. Install the
[WooCommerce extension](https://studio.inttegro.com/machine/ruby/extensions/woocommerce.md) when you need WooCommerce
customers, carts, orders, and refunds.

:::

## If a check fails

Confirm the product has an active price, re-save **Settings → Inttegro**, and
refresh the catalog cache before trying again. If checkout still does not open,
record the WordPress error and contact
[Inttegro support](mailto:support@inttegro.com) without including your API key.