Skip to content

Access scope

Before utilizing the REST API to access data from Genstore shops, all apps must declare the required access scopes and receive authorization from merchants. This document outlines the procedures for declaring and specifying appropriate access scopes.

Overview

Apps need to specify the scope of access needed for various business domains. Access is granted only after these scopes have been declared and authorized by the merchant. Below are the defined access scopes:

Access scopeMethodDescription
Business DomainBy DeclarationControls access to specific business domain data. Apps can access relevant REST APIs only after declaration and authorization. By default, the order domain returns only the last 60 days of order data and filters all protected fields.
All Order DataApproval RequiredAccess to complete order data, including data older than 60 days, requires an app and approval through the partner platform.
Protected FieldsApproval RequiredAccess to sensitive data (such as names, email addresses, etc.) requires an app and approval through the partner platform.

Business domain

During the app development phase, developers must declare which business domains their app needs access to. The following table outlines the available access scopes:

TIP

Select access scopes judiciously based on app needs. Excessive permissions can deter merchants from installing and using the app.

ScopePermissionsDescriptions
read_all_ordersRead-onlyCan query all orders, including orders from more than 60 days ago. Requires app approval in the Partner Platform Console.
read_ordersRead-onlyCan query orders from the last 60 days. To query orders older than 60 days, additional read_all_orders permission is required.
write_ordersRead-writeCan manage orders, including create, update, delete, and query operations. To query orders older than 60 days, additional read_all_orders permission is required.
read_productsRead-onlyCan query all product information.
write_productsRead-writeCan manage products, including create, update, delete, and query operations.
read_shopsRead-onlyCan query store data.
write_shopsRead-writeCan manage store data.
read_refundsRead-onlyCan query refund orders.
write_refundsRead-writeCan manage refund orders.
read_customersRead-onlyCan query customer information. Querying privacy-protected fields requires app approval in the Partner Platform Console.
write_customersRead-writeCan manage customers, including create, update, delete, and query operations.
read_discountsRead-onlyCan query discount information.
write_discountsRead-writeCan manage discounts.
read_gift_cardRead-onlyCan query gift card information.
write_gift_cardRead-writeCan manage gift cards.
read_appsRead-onlyCan query app information, including authorization scopes, message subscription information, and app details.
write_appsRead-writeCan manage apps, including authorization scopes, message subscription information, and app details.
read_fulfillmentsRead-onlyCan query order fulfillment information.
write_fulfillmentsRead-writeCan manage order fulfillment.
read_marketRead-onlyCan query market information.
write_marketRead-writeCan manage market.
read_finance_accountRead-onlyCan query finance account information.
write_finance_accountRead-writeCan manage finance accounts.
read_payments_transactionRead-onlyCan query payment transaction orders.
write_payments_transactionRead-writeCan manage payment transaction orders.

Order data

By default, the REST API provides access only to the most recent 60 days of order data. Accessing older order data necessitates an app for "Read All Order Data" and subsequent approval from the platform.

Apply for complete order data access

  1. Go to the partner platform's app console:
  2. Click API access permissions -> Data access request -> Read all orders data, then click the Request access button.
  3. Complete the access request form, providing a rationale for your app, and submit the form for review.

Protected fields

Protecting merchant and customer privacy is paramount when accessing sensitive information. Approval from the platform is required to access protected fields.

TIP

These restrictions are primarily for merchant stores. During the app development stage, simply submit your request for accessing protected fields for testing stores, without needing prior approval.

Protected fields

Protected fields include:

  • Name: First name, last name, and full name.
  • Email: User's email address.
  • Phone: User's phone number.
  • Address: User's address.

Apply for protected fields access

  1. Go to the partner platform's app console:
  2. Click API access permissions -> Data access request -> Protected customer data, then click the Request access button.
  3. Complete the access request form, providing a rationale for your app, and submit the form for review.

TIP

Select access scopes judiciously based on app needs. Excessive permissions can deter merchants from installing and using the app.