- Get Authorized Merchant Store List
Retrieves authorized merchant store list with basic store information and pagination data.
IMPORTANT: Valid access token required to access this endpoint.
Returns all authorized store information for the specified authorization ID with pagination support.
USE CASE: This endpoint is commonly used for store binding functionality, allowing service providers to retrieve authorized store details and bind them to their own systems for shop onboarding.
HOST: Keeta
DIRECTION:

Authorization ID that uniquely identifies a specific authorization session.
Each authorization generates a unique authId. There are two ways to obtain the authId:
1. Merchant authorization redirect - the authId is included in the redirect URL
2. Keeta Authorization Webhook - the authId is provided in the webhook payload
Please refer to the following for the specific workflow:Merchant Self-serve Authorization
- https://open.mykeeta.com/api/open/opendeliveryhttps://open.mykeeta.com/api/open/opendelivery/oauth/authorized/{authId}/merchantInfo
curl -i -X GET \
'https://open.mykeeta.com/api/open/opendelivery/oauth/authorized/{authId}/merchantInfo?pageNum=1&pageSize=10' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'X-App-Signature: YOUR_API_KEY_HERE'{ "userId": 12345678, "brandId": 1001, "brandName": "Sample Brand", "authorizedShops": [ { … } ], "page": { "pageNum": 1, "pageSize": 10, "totalPage": 1, "totalCount": 3 } }
Retrieves authorized merchant store list with basic store information and pagination data.
IMPORTANT: Valid access token required to access this endpoint.
Returns all authorized store information for the specified authorization ID with pagination support.
USE CASE: This endpoint is commonly used for store binding functionality, allowing service providers to retrieve authorized store details and bind them to their own systems for shop onboarding.
HOST: Keeta
DIRECTION:

Authorization ID that uniquely identifies a specific authorization session.
Each authorization generates a unique authId. There are two ways to obtain the authId:
1. Merchant authorization redirect - the authId is included in the redirect URL
2. Keeta Authorization Webhook - the authId is provided in the webhook payload
Please refer to the following for the specific workflow:Merchant Self-serve Authorization
- https://open.mykeeta.com/api/open/opendeliveryhttps://open.mykeeta.com/api/open/opendelivery/oauth/authorized/{authId}/merchantInfo
curl -i -X GET \
'https://open.mykeeta.com/api/open/opendelivery/oauth/authorized/{authId}/merchantInfo?pageNum=1&pageSize=10' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'X-App-Signature: YOUR_API_KEY_HERE'{ "userId": 12345678, "brandId": 1001, "brandName": "Sample Brand", "authorizedShops": [ { … } ], "page": { "pageNum": 1, "pageSize": 10, "totalPage": 1, "totalCount": 3 } }