Magento

Log in to your Magento admin panel at `yourstore.com/admin`. In the left sidebar, navigate to System → Extensions → Integrations. Click 'Add New Integration.' Fill in: - **Name**: give it a descriptive name like 'Bubble App Integration' - **Email**: enter a contact email (for notifications if the integration is revoked) - **Current User Identity Verification**: you may need to enter your admin password to confirm identity Switch to the 'API' tab in the Integration form. This is where you scope the token's access: - Under 'Resource Access,' select 'Custom' - Check the resources your Bubble app needs. For an order management dashboard: Sales (Orders, Shipments, Invoices), Catalog (Products, Categories), Customer (Customers). Do not grant 'All' unless absolutely required — least-privilege scoping reduces risk. Click 'Save.' Magento brings you back to the Integrations list — find your new integration and click 'Activate.' Magento shows the 'Integration Tokens for Extensions' popup with four values: 1. Consumer Key 2. Consumer Secret 3. **Access Token** ← this is the one you need 4. Access Token Secret Copy only the **Access Token** (the third value in the popup). This is what you paste into Bubble as the Bearer token. Consumer Key and Consumer Secret are for OAuth-based integrations — using them as Bearer causes 401 errors. Click 'Done' to close the popup. If you lose the Access Token, you must deactivate and re-activate the integration to generate new tokens — there is no 'show token' option.

1// Magento Integration activation generates 4 values:
2// 1. Consumer Key:       Use only for OAuth-based integrations
3// 2. Consumer Secret:    Use only for OAuth-based integrations
4// 3. Access Token:       ← USE THIS as the Bearer token in Bubble
5// 4. Access Token Secret: Use only for OAuth-based integrations
6
7// Correct Bearer format in Bubble API Connector:
8// Authorization: Bearer [Access Token value]   // mark Private
9
10// Base REST API URL formats:
11// Single default store:   https://yourstore.com/rest/default/V1/
12// Multi-store by code:    https://yourstore.com/rest/{store_code}/V1/
13// All stores (admin):     https://yourstore.com/rest/all/V1/
14
15// Verify access (test from browser with curl):
16// curl -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
17//   https://yourstore.com/rest/default/V1/store/storeConfigs
18// Expected: JSON array of store configuration objects

In your Bubble editor, go to Plugins → API Connector. Click 'Add another API' and name it 'Magento.' Set the base URL to `https://yourstore.com/rest` — this stops at `/rest`, not including the store scope or `/V1/`. The store scope and version go in each individual call's URL path. In the shared headers section for this API group, add: - Header name: `Authorization`, Value: `Bearer YOUR_ACCESS_TOKEN` — paste your Access Token after 'Bearer ', then check the **Private** checkbox - Header name: `Content-Type`, Value: `application/json` - Header name: `Accept`, Value: `application/json` Now add the Initialize Call. Click 'Add another call' and name it 'Get Store Configs.' Set method GET and URL path `/default/V1/store/storeConfigs`. This endpoint returns store configuration objects — safe to use as Initialize because it is read-only and returns useful data (store name, website ID, locale, base_currency_code). Click Initialize call. Magento returns a JSON array of store configuration objects. Bubble detects the array fields. If the Initialize call returns a 401, your Access Token is wrong (check you are using Access Token, not Consumer Key). If it returns 403, the Integration scope does not include Store configuration — add 'Stores' under API scopes and re-activate. For multi-store Magento: add a state variable `magento_store_code` (text, default 'default') on your Bubble pages and reference it in each call's URL path. In the URL field, type `/` + the state variable + `/V1/products` etc. Bubble evaluates the URL dynamically per workflow run.

1// Bubble API Connector: Magento
2// Base URL: https://yourstore.com/rest
3//   (do NOT include /default/V1/ here — it goes in each call)
4//
5// Shared Headers:
6// Authorization: Bearer YOUR_ACCESS_TOKEN   // mark Private
7// Content-Type: application/json
8// Accept: application/json
9//
10// Initialize Call: GET /default/V1/store/storeConfigs
11//
12// Expected response:
13// [
14//   {
15//     "id": 1,
16//     "code": "default",
17//     "website_id": 1,
18//     "locale": "en_US",
19//     "base_currency_code": "USD",
20//     "default_display_currency_code": "USD",
21//     "timezone": "America/Chicago",
22//     "weight_unit": "lbs",
23//     "base_url": "https://yourstore.com/",
24//     "base_link_url": "https://yourstore.com/",
25//     "base_static_url": "https://yourstore.com/pub/static/version1/",
26//     "base_media_url": "https://yourstore.com/pub/media/"
27//   }
28// ]

Magento's list endpoints use a bracket-notation filter system called searchCriteria. Unlike standard REST APIs where you pass `?status=pending`, Magento requires a nested bracket structure: ``` ?searchCriteria[filterGroups][0][filters][0][field]=status &searchCriteria[filterGroups][0][filters][0][value]=pending &searchCriteria[filterGroups][0][filters][0][conditionType]=eq ``` In Bubble's API Connector, these cannot be passed as a single URL parameter — you must add each bracket-key as a **separate URL parameter entry** in the call editor. Add a new call named 'Get Orders.' Set method GET, URL `/default/V1/orders`. Now add each filter parameter as individual entries: 1. Parameter: `searchCriteria[filterGroups][0][filters][0][field]`, Value: `status` (or make it dynamic) 2. Parameter: `searchCriteria[filterGroups][0][filters][0][value]`, Value: `pending` (dynamic) 3. Parameter: `searchCriteria[filterGroups][0][filters][0][conditionType]`, Value: `eq` 4. Parameter: `searchCriteria[currentPage]`, Value: `1` (dynamic) 5. Parameter: `searchCriteria[pageSize]`, Value: `20` (dynamic) 6. Parameter: `searchCriteria[sortOrders][0][field]`, Value: `created_at` 7. Parameter: `searchCriteria[sortOrders][0][direction]`, Value: `DESC` For the Initialize call, fill all dynamic fields with real values (status=pending, page=1, etc.) so Magento returns actual order data. Magento order list response: `{ "items": [ {...order objects...} ], "total_count": 247, "search_criteria": {...} }`. Map `items` in the API Connector to get the order list. Use `total_count` to build pagination — divide by pageSize and create a page number state variable. Magento's conditionType values: `eq` (equals), `neq` (not equals), `like` (contains, use `%value%`), `gteq` (greater than or equal), `lteq` (less than or equal), `in` (any of, comma-separated values), `notnull` (field exists). Standard operators like `>=` or `contains` do not work and return empty results without an error.

1// Magento → Get Orders
2// Method: GET
3// URL: /default/V1/orders
4//
5// URL Parameters (each as a separate entry in Bubble's API Connector):
6// searchCriteria[filterGroups][0][filters][0][field]         = status
7// searchCriteria[filterGroups][0][filters][0][value]         = pending     (dynamic)
8// searchCriteria[filterGroups][0][filters][0][conditionType] = eq
9// searchCriteria[currentPage]                                = 1           (dynamic)
10// searchCriteria[pageSize]                                   = 20
11// searchCriteria[sortOrders][0][field]                       = created_at
12// searchCriteria[sortOrders][0][direction]                   = DESC
13//
14// To add a date range filter (add as filterGroups[1]):
15// searchCriteria[filterGroups][1][filters][0][field]         = created_at
16// searchCriteria[filterGroups][1][filters][0][value]         = 2026-01-01 00:00:00
17// searchCriteria[filterGroups][1][filters][0][conditionType] = gteq
18//
19// Response:
20// {
21//   "items": [
22//     {
23//       "base_grand_total": 59.98,
24//       "grand_total": 59.98,
25//       "customer_email": "john@example.com",
26//       "customer_firstname": "John",
27//       "customer_lastname": "Doe",
28//       "increment_id": "000000042",
29//       "status": "pending",
30//       "created_at": "2026-01-27 14:32:00",
31//       "items": [ { "sku": "WT09-XS-Purple", "qty_ordered": 2, "row_total": 59.98 } ]
32//     }
33//   ],
34//   "total_count": 247
35// }

Add a call named 'Get Products' for the product catalog. Method GET, URL `/default/V1/products`. Add searchCriteria parameters: - `searchCriteria[filterGroups][0][filters][0][field]` = `status` - `searchCriteria[filterGroups][0][filters][0][value]` = `1` (enabled products only) - `searchCriteria[filterGroups][0][filters][0][conditionType]` = `eq` - `searchCriteria[pageSize]` = `20` - `searchCriteria[currentPage]` = `1` (dynamic) Magento product response: `{ "items": [{...}], "total_count": N, "search_criteria": {...} }`. Each product has `sku`, `name`, `price`, `type_id` (simple, configurable, grouped, virtual), `status`, `weight`, and a `custom_attributes` array. For **configurable products** (products with size/color variations): the parent configurable product has a NULL or zero price and NULL stock — price and stock live on child Simple products. To get child SKUs: GET `/default/V1/configurable-products/{sku}/children`. Each child has its own price and stock quantity. For stock quantity: GET `/default/V1/stockStatuses?searchCriteria[filterGroups][0][filters][0][field]=sku&searchCriteria[filterGroups][0][filters][0][value]={sku}&searchCriteria[filterGroups][0][filters][0][conditionType]=eq`. The response includes `items[0].qty` and `items[0].stock_status` (1=in stock, 0=out of stock). For a product price update: PUT `/default/V1/products/{sku}` with a body containing the complete product object — Magento requires full-object PUT, not partial updates. Fetch the product first with GET `/default/V1/products/{sku}`, modify the price field in a Bubble state, then PUT the complete modified object. For bulk price updates across many products, use 'Schedule API Workflow on a list' in Bubble to avoid the 30-second timeout.

1// Magento → Get Products
2// Method: GET
3// URL: /default/V1/products
4//
5// URL Parameters:
6// searchCriteria[filterGroups][0][filters][0][field]         = status
7// searchCriteria[filterGroups][0][filters][0][value]         = 1
8// searchCriteria[filterGroups][0][filters][0][conditionType] = eq
9// searchCriteria[pageSize]                                   = 20
10// searchCriteria[currentPage]                                = 1  (dynamic)
11//
12// Response (items array structure):
13// {
14//   "items": [
15//     {
16//       "id": 2048,
17//       "sku": "WT09-XS-Purple",
18//       "name": "Breathe-Easy Tank",
19//       "price": 34.00,
20//       "type_id": "simple",
21//       "status": 1,
22//       "visibility": 4,
23//       "custom_attributes": [
24//         { "attribute_code": "description", "value": "..." },
25//         { "attribute_code": "color", "value": "Purple" }
26//       ]
27//     }
28//   ],
29//   "total_count": 1854
30// }
31
32// Get configurable product children (for sizes/colors):
33// GET /default/V1/configurable-products/{parent_sku}/children
34// Returns array of simple product objects with individual price + stock
35
36// Get stock for a specific SKU:
37// GET /default/V1/stockStatuses?searchCriteria[filterGroups][0][filters][0][field]=sku
38//   &searchCriteria[filterGroups][0][filters][0][value]={sku}
39//   &searchCriteria[filterGroups][0][filters][0][conditionType]=eq

Updating an order's status in Magento from Bubble has a simpler path than most guides describe. The correct approach is NOT a PUT to the full `/V1/orders/{id}` endpoint (which requires a complete order object body). Instead, POST to `/V1/orders/{id}/comments` with a `statusHistory` body — this is the same endpoint Magento's own admin panel uses when a staff member changes an order status. Add a call named 'Update Order Status.' Set method POST, URL `/default/V1/orders/<id>/comments` where `<id>` is a dynamic text parameter for the Magento order ID (the numeric `entity_id`, not the `increment_id` display number). Set the body type to JSON. The required body structure: ```json { "statusHistory": { "comment": "Status updated from Bubble", "is_customer_notified": 0, "is_visible_on_front": 0, "parent_id": null, "status": "complete" } } ``` Set `is_customer_notified` to `0` to suppress customer email notifications during batch updates or testing; set to `1` when you want Magento to email the customer about the status change. For the Initialize call, you need a real Magento order ID (use one from your test orders list). The response is just `true` on success. For Bubble workflow: when a warehouse operator clicks 'Mark Shipped' on an order in your dashboard Repeating Group, use a workflow action: 'Plugins → API Connector → Magento → Update Order Status' with the entity_id from the current cell's data and status='complete'. Add a second workflow step to refresh the Repeating Group data or update the cell's displayed status via a custom state.

1// Magento → Update Order Status
2// Method: POST
3// URL: /default/V1/orders/<id>/comments
4//   (<id> = dynamic: Magento order entity_id, e.g. 1234)
5//
6// Body (JSON):
7{
8  "statusHistory": {
9    "comment": "<dynamic: optional internal note>",
10    "is_customer_notified": 0,
11    "is_visible_on_front": 0,
12    "parent_id": null,
13    "status": "<dynamic: new status string>"
14  }
15}
16
17// Common Magento order status values:
18// pending            → new order, not yet processed
19// processing         → payment confirmed, being fulfilled
20// complete           → shipped and delivered
21// closed             → refunded/returned
22// canceled           → canceled before fulfillment
23// holded             → held for manual review
24// payment_review     → payment flagged for review
25
26// Note: use the order's entity_id (numeric, e.g. 1234)
27//       NOT the increment_id (display number, e.g. 000001234)
28// The entity_id is in the 'id' field of the GET /V1/orders response

Before going live, test the full Bubble-to-Magento integration and address Adobe Commerce Cloud-specific requirements if applicable. **Adobe Commerce Cloud WAF:** Adobe Commerce Cloud (Magento hosted by Adobe) includes a Web Application Firewall (WAF) and CDN that may block API calls from unrecognized IP ranges — including Bubble's server IPs. If your API calls succeed with curl from your local machine but fail with HTTP 403 from Bubble, IP whitelisting is likely the cause. Contact your Magento system administrator or Adobe Commerce support to whitelist Bubble's IP ranges. As Bubble uses a multi-tenant infrastructure, the specific IP ranges vary — Bubble publishes current server IP ranges in their documentation. Request whitelisting of these ranges at the CDN/WAF layer, not just at the Magento application level. **End-to-end testing checklist:** 1. In Bubble's Logs tab → Workflow logs, verify all GET calls return 200 with populated data 2. Test searchCriteria filters by changing status values and verifying the returned orders match the filter 3. Test the order status update on a sandbox or staging Magento environment before production 4. For multi-store setups, verify that switching the store_code state variable returns products from the correct store 5. Test pagination: set currentPage to 2 and verify different products appear 6. Check Bubble's Workload Unit consumption in the Logs — complex searchCriteria calls and bulk product loads consume significant WU on high-traffic pages For complex enterprise Magento integrations — multi-source inventory, B2B quote management, ERP sync — RapidDev's team has experience with Magento API architecture at scale. Reach out at rapidevelopers.com/contact for a scoping call.

1// Multi-store Magento: switch store scope dynamically
2// Add a Dropdown on the page, data source = API Connector → Magento → Get Store Configs
3// Display field: code
4// On change: Set state 'magento_store_code' to Dropdown's value
5//
6// In all API Connector call URLs, reference the state:
7// URL: /<magento_store_code state>/V1/orders
8// URL: /<magento_store_code state>/V1/products
9//
10// Bubble Logs → check for WU consumption per call:
11// - Simple GET /orders (1 page): ~15-30 WU
12// - GET /products (large catalog): ~20-50 WU per page
13// - POST /orders/{id}/comments: ~10-20 WU
14//
15// Adobe Commerce Cloud IP whitelist request:
16// Provide Bubble's server IP ranges to your Magento admin for WAF whitelisting
17// Check Bubble documentation for current server IP ranges to whitelist
18// WAF whitelisting is done at the CDN level (Fastly, Cloudflare), not Magento config