Get a test marketplace

You build and test an integration against a real marketplace that you administer. The quickest way to get one is a free trial; it is the same product your client runs, with the same APIs.

Create the marketplace

1. Go to www.kreezalid.com/signup and fill in the form. The trial lasts 14 days and needs no credit card.

2. You land in the back office of your new marketplace. Its address is https://<subdomain>.mykreezalid.com, and the back office is under /admin.

3. In the set-up wizard, choose Start with sample data to get categories, listings and users to play with. Sample data can be deleted at any time from the back office home page, once you no longer need it.

Working for a client

If you build for an existing marketplace, work on a separate marketplace configured like theirs (same categories, attributes, order types and user groups) rather than on their live data. The MCP server can help you reproduce a structure from one marketplace to another.

Enable the APIs you need

API	What to do
Admin API	Settings → Account (/admin/settings/account) → API access → Generate secret key. See Authentication.
Front API	Nothing to enable. Create a member account and log in with it.
Partners API	Ask Kreezalid support for credentials for one of your test vendors.
Webhooks	Settings → Notifications (/admin/settings/notifications) → Webhooks. See Webhooks.
MCP server	Configuration → AI connectors (/admin/ai-connectors). See MCP server.

Create the users you need

Most integrations need at least one vendor and one customer:

1. Check the groups in Settings → Users → Groups (/admin/settings/users/groups). Note the id of a group that may post listings (your vendors) and of one that may not (your customers).

2. Create the accounts, from the back office or with the Admin API (POST /api/v1/users/add):

   curl -X POST https://acme.mykreezalid.com/api/v1/users/add \
     -u "$KREEZALID_API_KEY:$KREEZALID_API_SECRET" \
     -H "Content-Type: application/json" \
     -d '{
       "email": "vendor.test@example.com",
       "first_name": "Victor",
       "last_name": "Vendor",
       "group_id": 3,
       "password": "a-long-test-password"
     }'

   { "id": 4250, "message": "User created", "success": true, "content": [] }

   Without password, a random one is set: the user then needs Forgot password to sign in.

3. Use a real mailbox you control, or a plus-addressed one (you+vendor@example.com), for accounts that must receive emails such as order notifications.

Make test orders

To exercise order webhooks and order sync, place orders on the storefront as your test customer, with the payment method you will use in production configured in the back office. Then act on them as the vendor from the storefront, so that each step emits its webhook.

To move an order through its statuses without a real fulfilment, you can also update it with the Admin API. Status changes made this way emit no order.status.* webhook and send no email:

curl -X PATCH https://acme.mykreezalid.com/api/v1/orders/90311 \
  -u "$KREEZALID_API_KEY:$KREEZALID_API_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"status": "accepted"}'

{ "success": true, "message": "Order updated" }