Markets

markets let a single bot serve different ui, greeting, and responses per location you select which market to load by passing a market slug to start( ) the backend is told the same market so it can localize the conversation (greeting and responses) market is required you must pass the market slug configured for your bot — there is no default and no fallback find your market slugs in the kindly platform (settings → general → details & markets) selecting a market pass the market slug (as configured in the kindly platform, e g eu , us , general ) when you initialize the sdk kindlysdk start(botkey "your bot key", languagecode "en", market "eu") with authentication kindlysdk start(botkey "your bot key", languagecode "en", market "eu") { chatid, promise in promise fulfill("jwt token") // market + auth callback } what the sdk does with the market settings — it loads the market specific settings (theme, greeting config, compliance, localization) from /settings/{botkey}/{market} json connect — it includes the market in the /connect request so the backend serves the greeting and bot responses configured for that market no fallback settings are always market scoped the sdk loads the requested market's settings (with retries); if they can't be loaded, settings loading fails and the chat will not load there is no fallback to another market and no base/per bot settings file outside of markets — make sure the slug you pass exists and has published settings for your bot notes the market is fixed for the lifetime of the session to switch markets, call start( ) again with a different market (the sdk reinitializes just as it does for a bot key change) the market does not change the language use languagecode / setlanguage( ) for language; use market for the location specific content set for initialization basics, see initialization initialization md