Product Options API for Shopify: What the API Gateway Does and When Complex Stores Need It

Learn what the Aris Product Options API provides, how Public API and Webview work, and when Shopify stores need custom integrations.

Arisify Global Team Nov 18, 2026 5 min read
Product Options API for Shopify: What the API Gateway Does and When Complex Stores Need It

In this article

  1. 01What is a product options API?
  2. 02What data does the Aris Product Options API provide?
  3. 03Public API vs. Webview API: What's the difference?
  4. 04When does a Shopify store need a product options API?
  5. 05Which Aris plan includes API access?
  6. 06What should developers check before integrating?
  7. 07Frequently asked questions
  8. 08Connect product options to your store's systems

What is a product options API?

A Shopify product options app lets merchants collect customer choices such as engraving text, file uploads, dimensions, and paid add-ons. As a store grows, those configurations may also need to connect with external systems or custom storefronts.
A product options API provides a structured way for other applications to access or display this information.

Aris Product Options offers two integration capabilities:

  • Public API: Retrieves option sets, app settings, and localization data for server-side integrations.

  • Webview API: Displays Aris options in custom storefronts, themes, widgets, and other frontend experiences.

The term API gateway can describe this connection in general. However, Aris's official documentation calls these features Public API and Webview API, rather than a separate product named API Gateway.

What data does the Aris Product Options API provide?

The Public API uses the base URL:
https://public-api.avisplus.io/api/public/v1
Its documented endpoints are:

Endpoint

Purpose

GET /option-sets

Retrieve a list of option sets

GET /option-sets/:id

Retrieve a specific option set

GET /settings

Retrieve app and storefront settings

GET /localizations

Retrieve translated interface strings

An option set can include field labels, input types, required status, selectable values, additional prices, validation rules, and conditional display settings.
For example, a furniture configurator could retrieve a product's material selector, engraving field, and conditional gift-message option.
Important: These documented endpoints retrieve configuration and settings. They are not documented as endpoints for creating orders, retrieving customer submissions, or updating fulfillment status. Those workflows need the relevant Shopify order data or another supported integration.

Public API vs. Webview API: What's the difference?

The two APIs support different integration environments.

Public API

Webview API

Main purpose

Retrieve option configuration

Display Aris options in a custom frontend

Environment

Backend / server-side

Storefront / browser

Token

API Token

Webview Token

Minimum plan

Advanced

Premium

Example use

ERP, reporting, internal tools

Custom product page, headless storefront, embedded widget

Rate limit

60 requests/minute

600 requests/minute

Public API: For backend integrations
An authorized backend can retrieve Aris option sets and use their configuration in systems such as ERP, OMS, 3PL, reporting tools, or internal applications.
The API Token is a secret credential. Keep it on the server rather than exposing it in browser code or public repositories.
Webview API: For custom storefront experiences
Webview is relevant when a merchant wants to display Aris options outside the standard app-block presentation---for example, in a custom product page, embedded widget, or headless storefront.
The Webview Token is intended for browser-facing use on approved domains added to its whitelist.

When does a Shopify store need a product options API?

Not every merchant needs API access. If the standard Aris storefront display and Shopify order workflow meet the store's requirements, built-in functionality may be enough.

API access becomes more useful when product configuration is part of a larger technical workflow.

  1. ERP and order-management workflows
    A backend can retrieve option configurations to keep product rules aligned across systems. For example, a furniture retailer may need its internal tools to reference the same material, finish, and dimension options shown on Shopify.

  2. Custom production workflows
    Personalized products may require configuration details to support production. However, developers must separately identify how to retrieve each customer's submitted choices: the documented Public API does not list an order retrieval endpoint.

  3. Custom configurators and headless storefronts
    Stores building a tailored product experience can use Webview to display Aris options in a custom frontend instead of relying only on the standard app block.

  4. Internal tools and reporting
    The Public API can supply option-set configuration for internal dashboards or reporting workflows. Building those tools and combining the data with other business information still requires development.

One distinction is especially important: option configuration describes what customers can choose; order data describes what a particular customer actually selected. The documented Public API covers configuration, not a complete order-management workflow.

Which Aris plan includes API access?

Public API access starts with Advanced. Webview and webhook access are available on Premium.

Plan

Public API

Webview

Webhooks

Included API calls

Free

No

No

No

—

Pro

No

No

No

—

Advanced

Yes

No

No

5,000 / billing cycle

Premium

Yes

Yes

Yes

25,000 / billing cycle

The Shopify App Store listing shows standard pricing of $24/month for Advanced and $59/month for Premium. Shopify Plus pricing may differ.

Before choosing a plan, keep these limits in mind:

  • Billing cycle: Usage resets every 30 days according to the app billing cycle.

  • Shared quota: Premium API Token and Webview Token requests share the same 25,000-call allowance.

  • Rate limits: Public API supports 60 requests/minute per shop; Webview supports 600.

  • Overage: The documented policy lists additional 5,000-call blocks at $5 for Advanced and 25,000-call blocks at $10 for Premium, subject to the approved spending cap.

Aris also documents limited testing quotas for eligible trial and development stores. Check the current API policy for eligibility and exact conditions before planning a test environment.

What should developers check before integrating?

Before building, clarify four things:

  • Data needed: Does the system need option configurations, translations, customer selections, or order records?

  • Integration direction: Does it only need to read data, or must it also create or update information?

  • Environment: Is this a server-side integration (Public API) or a browser-facing storefront experience (Webview)?

  • Expected usage: Estimate requests per product page, sync job, or update event before selecting a plan.

Developers should review the API & Webview reference and Swagger documentation for current request and response schemas. Aris documentation states that API tokens are issued by the Aris team rather than generated directly in the app interface.

Frequently asked questions

Does Aris have a product options API for Shopify?

Yes. Public API retrieves option sets, settings, and localization data. Webview displays Aris options in custom storefronts and frontend experiences.

Which plan includes API access?

Advanced includes Public API access and 5,000 calls per billing cycle. Premium includes 25,000 calls, Webview, and webhook access.

Can the API retrieve customer orders?

The documented Public API does not list order retrieval or fulfillment-update endpoints. Developers need to use the appropriate Shopify order or fulfillment data source for those workflows.

Is Webview the same as Public API?

No. Public API is designed for server-side access to configuration data. Webview is designed to display options in custom frontend experiences.

Connect product options to your store's systems

Aris Public API helps backend systems access option configurations, settings, and localization data. Webview supports custom storefronts that need to display Aris options in a tailored frontend.
The right solution depends on the integration: Advanced provides Public API access, while Premium adds Webview and webhooks with a larger usage quota.

Before development starts, identify exactly which data the external system needs, especially whether it needs option configuration or individual customer order data.

Ready to put this into practice?

Explore the Arisify Global app portfolio or visit the Help Center for detailed setup guides.