A guide to publishing digital products, managing versions, buyer access, licenses, and developer tools. It contains the essential information needed to work with the Byteory platform.
Products
Publishing and moderation
Versions
Files and updates
Developer
Applications and keys
Getting started
The seller workflow consists of creating a product, filling in information, submitting it for moderation, and publishing updates afterward.
Enter a name, category, description, and price.
Upload images, the main file, and additional links.
A moderator will review the content and listing accuracy.
After approval, add new releases and changelogs.
Recommendation
Before submitting, review the listing from a buyer’s perspective: make sure the product purpose, file delivery terms, requirements, compatibility, and payment format are clear.
The product listing is the main page where the buyer decides whether to purchase. The more complete the information, the fewer questions arise before checkout.
Please note
Do not include false promises, unavailable features, hidden terms, or materials you do not have distribution rights for.
After submission, the product enters the review queue. Until approved, it is not shown in the public catalog and is unavailable to new buyers.
The listing was sent to a moderator and temporarily hidden from the catalog.
The product is published and available to platform users.
Fix the listed issues and resubmit the product.
Each new version may contain a separate file, release number, changelog, compatibility information, and additional buyer instructions.
Version example
v2.4.0
StableVersion history is displayed on the product page. The buyer can view the publication date, changelog, and files available to them.
After a successful purchase, access to the product is linked to the user’s account. Purchased materials appear in the library and remain available under the seller’s terms.
The product owner can track sales, views, and buyer activity. These data help evaluate listing, update, and advertising performance.
Product page interest
Number of completed purchases
Seller earnings amount
Ratings and feedback
For developers
The @@PROTECTED_1@@ section is intended for managing applications, access keys, callback addresses, and future API integrations with the platform.
Create a separate application for each website, dashboard, Discord bot, or other external service.
The key identifies your application when calling permitted platform endpoints.
The callback address is used to return the user or pass the authorization result to an external application.
In the future, applications will be able to receive events about orders, licenses, updates, and other platform actions.
Never publish secret keys
Store keys only on the server. Do not put them in public JavaScript, GitHub repositories, screenshots, or support messages.
Use a unique password, two-factor authentication, and regularly review active devices to protect your account and products.
Use a strong password and enable additional sign-in verification.
Grant applications only the permissions they actually need.
If you notice suspicious activity, revoke the key and create a new one.
Need help?
Check the profile sections and product page, or contact administration through the available channels. Include a description of the issue, a page link, and screenshots if they help explain the situation.