Amazon: connect and revoke
The authorized operator of each selling account signs in to Seller Central, checks this application and permissions in the official OAuth screen, and grants consent. Enter passwords only on official Amazon pages. Revoke in Seller Central’s Apps and Services / Manage Your Apps. Collection and access stop; all copies are deleted within 30 days of the earliest deletion trigger.
Amazon public applications require seller reauthorization every 365 days and anytime a role is added to the application. We notify the registered email before expiry and when a role is added. An authorized selling-account operator selects this application’s Re-Authorize action in Seller Central’s Apps and Services / Manage Your Apps, reviews and accepts the requested permissions, and completes sign-in on our website if required. When authorization expires or becomes invalid, we stop API collection, access and synchronization for that account. Processing that uses an added role starts only after reauthorization for that role. After reauthorization, we update the tokens, verify the account, permissions and connection, and resume processing.
Amazon official reauthorization guide
Application sign-in address after service launch: https://app.grtllc.jp/oauth/amazon/login. Please contact us about when applications open.
Yahoo! Shopping: prepare
Prepare the store account and the Yahoo! JAPAN ID of an authorized employee registered in that store’s SCPro. Prepare a separate public key for each store; never reuse another store’s key or account. Public keys expire one year after issue. Before expiry, a store operator with tool-management authority issues a replacement and updates integration settings with our instructions.
Yahoo! Shopping: authorize
Check the application name, operator, requested permissions and website/terms/privacy links in the official consent screen. Enter passwords only there. After returning, verify the store and connection. The application server handles callbacks over HTTPS. Never send secrets, tokens or purchaser data to support.
Yahoo! Shopping: renewal and operation
Yahoo! Shopping requires store reauthorization every four weeks. We notify the registered email before expiry and stop the affected store’s API processing when authorization expires. Processing resumes after reauthorization and verification of the store, permissions and connection.
For official API and public-key update notices, check the email displayed in the profile page after Business ID integration, or the Business Manager email before integration. No saved purchaser copies exist; use SCPro for store operations when the API is unavailable.
Yahoo! Shopping: disconnect
Disconnecting stops that store’s API calls immediately and deletes credentials held by us. Withdraw Yahoo! JAPAN consent separately in the official interface; our deletion alone does not guarantee instant invalidation of all tokens. If one Yahoo! JAPAN ID authorizes several stores, check the scope of the withdrawal action. Support also accepts store-specific disconnection requests. Disconnection and billing cancellation are separate.
Data handling and credit display
We do not retain any Yahoo! Shopping purchaser personal information, without exception. Order numbers, related identifiers, products, statuses and inquiry text that may identify a purchaser are subject to the same restriction. They are excluded from databases, files, logs, caches, backups and persistent sessions. Other information supplied by LY Corporation through the Shopping Store API or test API is also not retained unless LY Corporation separately instructs its storage. Such instructions apply only to other information and never to purchaser personal information. Any instructed storage is limited to specified fields, purposes and periods.
Features involving purchaser information follow lawful store instructions and the non-retention obligation in Article 10. Temporary memory processing is limited to what is necessary, and information is discarded when processing ends. It is never recorded in databases, logs, caches, queues, files or backups. Purchaser-data storage, file exports and saved shipping labels are outside the feature scope.
Our policy requires applicable Yahoo! Developer Network credit, linked to the official site, on API-powered screens under the applicable display rules. Credit identifies the technology used and does not imply official certification or partnership.
Web Services by Yahoo! JAPAN （https://developer.yahoo.co.jp/sitemap/）