external_user_id
when beginning a new round of testing to ensure you link a new merchant account.type: link
and a dummy external_user_id
that you will use in subsequent API requests.KnotConfiguration
, pass the session in sessionId
and a merchantId
for a merchant of your choosing. In your implementation, merchants are retrieved via List Merchants by passing type: shopping
. For testing purposes, you can likely hardcode a single merchantId
for a merchant.user_good
/ pass_good
. Once your merchant account is successfully linked, you will receive the AUTHENTICATED
webhook event.AUTHENTICATED
webhook event, make a request to Sync Cart with the same external_user_id
& merchant_id
as you used in prior steps and a dummy products.external_id
. Optionally, pass a delivery_location
as well in the request.Optionally, send simulate: failed
in the request to simulate receiving a SYNC_CART_FAILED
webhook event.SYNC_CART_SUCCEEDED
webhook event.Optionally, make another request to Sync Cart with the fullfillment.id
of an alternative fulfillment option received in the webhook.SYNC_CART_SUCCEEDED
webhook, make a request to Checkout with the same external_user_id
& merchant_id
as you used in prior steps and optionally a payment_method
object.Optionally, send simulate: failed
in the request to simulate receiving a CHECKOUT_FAILED
webhook event.CHECKOUT_SUCCEEDED
webhook event.transactions.id
value(s) from the CHECKOUT_SUCCEEDED
webhook event and make a request to Get Transaction By ID for each transaction to retrieve the transaction information.Most merchants generate a single transaction for a purchase, but some generate multiple.