Account and Profile
Pull the profile to view name, status and linked channels; this aligns with the bee99 App's internal flow
Example: GET /api/v1/account
Set up API, webhook and integration quickly with bee99 App
bee99 APK Download bee99 Register
The setup is usually started by Dhaka-based developers in about 10 minutes
From account panel, get key and secret, then first call in test env
Follow the endpoint list in the documentation, test GET and POST separately
The webhook will hit on event, so add retry and signature verification beforehand
These numbers clearly show the flow
From 88,978 reviews this score comes; users prefer stable performance the most
When live traffic is high, caching and batching prove very useful; many Dhaka teams say the same
With the same API you can pull multiple feeds, making both the app and web panel light
The service has been running since 2017, so webhook retry and status checks keep the flow stable
Most of the work is done with four main calls
Pull the profile to view name, status and linked channels; this aligns with the bee99 App's internal flow
Example: GET /api/v1/account
A 301+ titles list may come from here; cache the category, thumbnail and update time
Example: GET /api/v1/catalog
Verify each response's signature to catch wrong calls; keep small validation before timeout
Example: POST /api/v1/verify
Combine the login session and device token together so the bee99 Login flow and app session are not separate
Example: POST /api/v1/session-sync
Keep the token short; security is most important here
Put the token in the header for every request; rotate token, old key cancels immediately
Example: Authorization: Bearer <token>
Verify payload hash and secret together to prevent webhook spoofing
Example: X-Signature header
When logging in from mobile, the device id is used; Android users see fewer session mismatches.
Example: pass the device_token
Fast calls are good, but control is better
Don't send many requests at once; a 1 to 2 second gap keeps the queue intact.
If 429, use backoff; many small teams in Dhaka reduce call loss this way
Cache data that changes little; this makes the bee99 App panel open faster
Data arrives on event
When status changes, the server sends a webhook, reducing polling and speeding responses
Example: event=status_changed
If Receiver 200 fails, the message will retry; Nagad and Rocket teams prefer this pattern
Example: retry_count=3
Separate the order, profile, and session maps; later debugging takes less time
Example: webhook_topic=session.updated
Start with two simple libraries
A good fetch wrapper for the web dashboard makes error handling much easier
Works on old servers too; Dhaka's small team still runs a PHP panel
It takes 5 minutes to create a test request; then run the flow without copy-paste
Send a call to a local endpoint and debug; start with plain URL, not QR
Small things in a local setup matter
Many teams test on both office WiFi and mobile data; this helps understand live call behavior beforehand
Keep the local top-up flow in a separate module; unify Rocket-based Nagad and bKash status messages in one line
Some users on 3G have small payloads, compressed images, and cache policy helps here
If the API is ready, download bee99, register bee99, and integrate together
Download bee99 APK now Download bee99 AppFlow on one screen, webhook status on another