Store Authorization Notification

Store Authorization Notification
Webhook

Request

This webhook is sent by Keeta to notify the vendor's system when a merchant grants authorization for a store. This event is triggered when a new store is added to the merchant's authorized store list. This event is triggered when a merchant adds one or more stores to an existing brand authorization. For example, when stores were not fully included during the initial authorization and are subsequently added.

Event ID: 1301

Notes: Authorization in Keeta is managed at the brand level, and each brand has a single access token. Expanding the store scope does not affect the existing token.

Bodyapplication/jsonrequired

appIdinteger, (int64)required

Unique application ID assigned by Keeta.

Example:3762772727

shopIdinteger, (int64)required

Unique identifier of the store that has been added to the authorization scope.

Example:145541

shopNamestringrequired

Name of the shop, provided for identification purposes.

Example:"Downtown Store"

authIdstringrequired

Authorization record ID, which can be used for batch store mappings. When a merchant authorizes multiple stores in a single operation, Keeta sends one notification per store. The authId is shared across all notifications from the same authorization batch, allowing the developer to identify which stores were authorized together.

Example:"auth_20240324_001"

createTimeinteger, (int64)required

Time when the event occurred, specified as milliseconds since Jan 1, 1970 (Unix epoch).

Example:1711267200000

opTypeintegerrequired

Operation type. Always 1 for this event (store authorization added).

Example:1

Payload

{
  "appId": 3762772727,
  "shopId": 145541,
  "shopName": "Downtown Store",
  "authId": "auth_20240324_001",
  "createTime": 1711267200000,
  "opType": 1
}

Responses

Request executed successfully

Bodyapplication/json

codeintegerrequired

A numeric status identifier indicating the result of the interface call, used to determine whether the operation executed successfully.

Enum Value	Description
0	The request was executed successfully.
Non-zero value	The request execution failed. Specific error details can be viewed in the message field.

Example:0

messagestringrequired

Text description corresponding to the status code, explaining the operation result or error cause to users.

Example:"Success"

Response

{
  "code": 0,
  "message": "Success"
}