Using the Store App Content API (News, Pages, and Business Info)
Purpose of this guide
This guide covers how to use /api/v1/apps/{shopId}/* to fetch the content shown by the store app (web renderer, LINE mini app, and iOS / Android apps) — news, pages, app manifest, business info, and membership card config.
shopId is the business account IDThere is one store app per business account. For the
{shopId} in these endpoints, pass the organizationId returned by GET /api/v1/me/organizations as-is. shopId and the business account ID are the same value, and are distinct from the store ID (storeId). There is no procedure or dedicated field for resolving shopId from a store ID.
Endpoint list
| Method | Path | Purpose | Scope |
|---|---|---|---|
| GET | /api/v1/apps/{shopId}/manifest | App appearance, theme, nav, and per-platform form IDs | Per business account |
| GET | /api/v1/apps/{shopId}/posts | News (announcements) list | Per business account |
| GET | /api/v1/apps/{shopId}/pages | Published pages list | Per business account |
| GET | /api/v1/apps/{shopId}/pages/{slug} | Page detail (by slug) | Per business account |
| GET | /api/v1/apps/{shopId}/business-info?storeId={storeId} | Business hours, special business days, and current open status | Per store |
| GET | /api/v1/apps/{shopId}/membership-card-config | Membership card / wallet config | Per business account |
Example: fetching news
Pass the business account ID as {shopId}.
GET /api/v1/apps/{organizationId}/posts?status=Published&take=20News, pages, and the manifest are per business account. Whichever store under the same business account is selected, the same content is returned (it is not split per store).
Example: fetching business info (per store)
Because business hours differ per store, storeId must be passed as a required query parameter.
GET /api/v1/apps/{organizationId}/business-info?storeId={storeId}&specialDaysAhead=30storeId is the store ID returned by GET /api/v1/me/organizations/{organizationId}/stores.
About the store → shopId mapping
The app already holds both organizationId and storeId through its "select a business account → select a store" flow. Pass them to the content API as follows.
- News, pages, manifest, membership card config → pass
organizationIdas{shopId}(no store needed) - Business info → pass
organizationIdas{shopId}and the store ID in thestoreIdquery
Authentication
The content read endpoints are public (because the content itself is public information), so no OAuth token is required. If you already know the business account ID inside the app, you can call them directly.
About creating news
At present, posts is read-only (there are no create/update endpoints from the API). News is edited from the Receipt Roller admin screens. If store staff should be able to post news from the app in the future, a write endpoint and a dedicated scope will be added separately.
Related guides
- Listing business accounts, stores, and POS terminals — where to obtain
organizationId/storeId - Using the Business Hours API
- Back to the developer help top
-
Using the Store Information APIA guide to the REST API for fetching and updating a store's basic information (store name, store type, contact details, and address). Lets you implement a store information editing screen from token-authenticated clients such as staff apps.
-
PosTransactionDto specification — field reference for transaction dataA complete field reference for PosTransactionDto, the canonical model for the transaction data ReceiptRoller handles. For each category — identifiers, dates, amounts, line items, payments, staff, status, and CRM linkage — it summarizes the field names, types, meanings, and how each POS vendor populates them. A reference for developers and external-system integrators. Also referenced from the Smaregi and Square mapping articles.
-
Purchase and receipt data integrationExplains the structure of the purchase and receipt data ReceiptRoller handles, how to retrieve it, related scopes, Webhooks, and common use cases.
-
Using the Business Hours APIA guide to ReceiptRoller's Business Hours API (/api/v1/stores/{storeId}/business-hours). Covers retrieving and updating per-day business hours, registering special business days (temporary closures and hour changes), configuring a store's workable hours (the upper bound for shift creation), and determining whether the store is currently open.
-
Using the Orders / OMS APIA guide to CRUD operations on the orders under a business account using ReceiptRoller's Orders / OMS API (/api/v1/orders). Covers creating, updating, transitioning status (confirm, process, cancel), and deleting orders, plus the flow for Android / iOS apps and server integrations.