Register / Update Merchant endpoint info.

Request

Register and update the Merchant endpoint GET /v1/merchant information in Keeta.

For the Software Service, all authorized merchant will use the same token. To enable Keeta to identify which merchant needs to be registered, the Software Service must include the Keeta merchant ID in its requests. The Software Service should also save the mapping relationship between the Keeta merchant ID and its own merchant ID in the system. Merchants can obtain this merchantId from the Keeta merchant portal.

IMPORTANT:
It is necessary to provide the Keeta merchant ID to ensure that the mapping between the merchant ID of Software Service and the merchantId of Keeta is accurate.
If an existing Keeta MerchantId or External MerchantId under the App has been previously registered, any subsequent onboarding request containing these identifiers will result in the deletion of historical data and the creation of a new mapping configuration.
Store registration via onboarding endpoint must be completed prior to order flow integration. This enables Keeta to properly identify the merchantId in your system. Otherwise, no order events will be received via polling or webhook.

HOST: Keeta

DIRECTION:

Security

OAuth2(Required scopes: od.all) and Sig

Query

merchantIdstringrequired

The ID of the Merchant for whom you want to complete or change registration info.

Bodyapplication/jsonrequired

getMerchantURLobject

Information about the merchant's Software Service's GET /v1/merchant access. This endpoint has the necessary information for Keeta to be able to make the merchant's available on their plataform.

ordersWebhookURLstring, (uri)

Information about the merchant's Software Service's POST /v1/newEvent webhook access. This is where Keeta will sent the order's events to the Software Service as they happen.

keetaMerchantIdnumberrequired

The Keeta merchant ID is generated by Keeta. Merchants can obtain this merchantId from the Keeta merchant portal.

curl -i -X PUT \
  'https://open.mykeeta.com/api/open/opendelivery/v1/merchantOnboarding?merchantId=string' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'X-App-Signature: YOUR_API_KEY_HERE' \
  -d '{
    "getMerchantURL": {
      "baseURL": "http://example.com",
      "apiKey": "string"
    },
    "ordersWebhookURL": "http://example.com",
    "keetaMerchantId": 0
  }'

Responses

Resource has been created.

Bodyapplication/json