Setup
Connect Tebex to Discord in three steps
Invite the bot, add your store with its public webstore token, then pick a channel. Nothing is posted until that last step.
- 1
Invite the bot
Pick your server and approve it. Discord will show you three permissions, and these are them.
- View Channel So it can see the channels you point a feed at.
- Send Messages So it can post the announcement.
- Embed Links So the announcement renders as a card.
It cannot read your messages, cannot see your member list, and cannot see who is online. Discord does not give it access to any of that.
- 2
Run /tebex add
Three required options: your public webstore token, the links style, and the first channel. The command replies privately, so the token never lands in a channel other people can read.
Getting the token right is the part worth slowing down for. It is covered in full below.
- 3
Pick your channels
Run
/tebex channelonce per feed you want. Each feed gets its own channel, and any feed you skip stays off.- New packages
- Sales and price drops
- Community and payment goals
- Catalogue changes (removed, expiring, categories)
- Server status
- 4
Optional: check it first
/tebex previewrenders a real announcement privately, so you can confirm the link button works before anything goes public. Then/tebex healthwill tell you whether your listing is in a state worth announcing.
Aurora Roleplay
🆕Gold Rank
Priority queue on every server, a coloured name tag, and access to the /kit gold command once per day. • Priority queue • Coloured name tag • Daily gold kit • Access to the members-only lounge
Price
$24.99
Type
One-time
Category
Ranks
New package • Details shown as of posting • Today at 14:32
What lands in the channel once step three is done.
Step two, in full
Where the public token comes from
The page you have to visit shows your private key right next to the public token. Only the public one is wanted, and only the public one will be accepted.
- 1
Open your Tebex Creator Panel, then Integrations, then API Keys.
- 2
That page shows two values. The one VendFeed wants is the one labelled Public Token, described by Tebex as “the key used to access any public facing APIs”.
- 3
Go by that label, not by what the value starts with. Prefixes differ between stores, so a token that looks nothing like somebody else’s can still be the right one.
This onePublic Token
The key used to access any public facing APIs. This token is allowed to be shared publicly if required to do so by the API integration.
Not thisPrivate Key
The key used to access any APIs that require authorisation. This key should never be shared publicly.
The value above is an example. Prefixes differ between stores, so go by the field label rather than by the first few characters. If you have never generated a private key, that row shows a Generate button and no value at all, so there is nothing there to copy by mistake.
- 4
The private key is never needed, and VendFeed will not accept it.
What the public token can do
The public token grants nothing a shopper visiting your store cannot already do. It reads your listings and it can start a basket.
It cannot see your revenue, your customers, your payment details or your settings. It cannot change anything, and it cannot be used to issue a refund or a command. The private key is the one that does all of that, and VendFeed neither asks for it nor accepts it.
Still treat the token as yours
Do not paste it into a public channel. /tebex add replies privately for exactly that reason, and VendFeed only ever shows a stored token masked, never in a log line or a shared channel.
Link styles
What the button on each card points at
Tebex webstores differ in what they can deep link to, so setup asks which to use.
Package
Straight to the item. The best experience where your storefront supports it.
Category
To the category the package sits in. A good middle ground for storefronts without package pages.
Store front page
To the storefront itself. Always works, whatever your store is built on.
The setup reply shows you an example URL so you can see where the button will go, and /tebex preview renders a real announcement privately so you can click it. If a package has no page of its own it falls back to the category, then to the front page, rather than giving you a dead button, and every link is checked before it becomes one.
Requirements
What you need, and what the bot asks for
VendFeed is hosted, so there is nothing to install and nothing to run. A Tebex webstore and a Discord server is the whole list.
What the bot asks for
- Permissions
- View Channel, Send Messages, Embed Links. It does not manage roles, channels or anyone else’s messages.
- What it cannot see
- Your messages, your member list, or who is online. Discord does not give it access to any of it.
- Slash commands
- Added to your server on the way in, so
/tebexand/storework straight away.
What you need
- A Tebex webstore
- With access to its public token in the Creator Panel.
- A Discord server
- Where you can add a bot, which means Manage Server or Administrator.
- Hosting
- None. VendFeed is hosted and run by Digital Den as one shared bot, so there is nothing to download, deploy or keep online, and no version to keep up to date.
- Cost
- Nothing for 1 store per server. A paid plan is planned for larger setups, but nothing about it is settled yet.
Ready when you are
Three permissions, one public token, and nothing posted until you pick a channel.