It only describes pages that exist in the app: the same groups and link titles as in the sidebar (Wallet & Purchases, SIM & Cloud, Devices, History, Developer, Security). The marketing site states you can use features from the dashboard without code, and only need a developer if you use the API on your own site or app — this guide follows that split.
Wallet means the balance you fund inside the app; buying airtime or data uses that balance (the site also describes funding the wallet when the SIM has no data). VTU on the site means virtual top-up airtime; AWOOF data is one of the data product types called out there.
Register or log in from the main website. After login you normally open Dashboard from the sidebar (or land there first). Use it to see balance and recent activity before you start buying or changing settings.
Quick Guide in the sidebar points to this page. You can still download the PDF if you prefer an offline copy.
Service Charges & Pricing lists charges as shown in the app — check there before you fund or quote someone.
Fund Wallet is where you add money to your wallet balance. Credits and debits appear under History → Transaction History → Wallet History.
Under Wallet & Purchases:
- Buy Airtime — VTU-style airtime; pick network, number, and amount, then submit.
- Buy Data — data bundles; pick plan and recipient number.
- Buy AWOOF Data — AWOOF data bundles when that product is available in the form.
Each screen has its own fields; double-check network and phone number before you submit. Cost comes out of your wallet.
Use this block when you link SIMs or cloud flows — skip it if you only use the wallet.
- MOMO(502 & 671) ☁️ SETUP — MoMo cloud setup page.
- Sim Connection → Link SimCard
- MtnDataShareSystem → Link Sims, Manage Sims, DIY - Vending, History
- Dispense Methods — how orders are fulfilled (paths you configure here).
- Plans Id's — plan identifiers (useful with API or when the product list refers to IDs).
For device-based SIM hosting (the site mentions a companion Android app).
- Devices — device management.
- Device Base License — licensing for the device.
- SimCards Pins — SIM PIN storage.
- Download App — download the app linked from the dashboard.
- Under History → Transaction History → Devices' Inbox for device-related messages.
Open History → Transaction History, then pick the list that matches what you did:
- Vtu/Momo/Sns/Ussd
- Data TopUp
- Stock History
- Glo[DG] Cloud
- Devices' Inbox
- Wallet History
Developer (sidebar heading):
- Api Key — key for API requests (the FAQ on the marketing site says you only need a developer for API integration).
- Set Webhook URL — callback URL you configure.
- Api Documentation — opens the Postman documentation URL linked in the app.
Security:
- Whitelist IP — allowed IPs for API access as set on that page.
- Error Management — errors you can retry or handle there.
- Log out — bottom of the sidebar; ends your session.
FAQ — Ogdams SimHosting SIM hosting & VTU dashboard
What does this Ogdams SimHosting quick guide cover?
It explains how to use the logged-in dashboard: Wallet & Purchases (pricing, fund wallet, buy airtime and data), SIM & Cloud (MoMo setup, link SIMs, dispense methods, plan IDs), Devices, History, Developer (API key, webhook, API docs), and Security (IP whitelist, error management, logout) — using the same sidebar labels as in the app.
How do I buy VTU airtime and data bundles?
Fund your wallet under Fund Wallet, then use Buy Airtime for VTU-style airtime or Buy Data / Buy AWOOF Data for bundles. Cost is deducted from your wallet; confirm network and phone number before submitting.
Where are SIM hosting and cloud setup in the dashboard?
Under SIM & Cloud: MoMo cloud setup (502 & 671), Link SimCard, MtnDataShareSystem (link/manage SIMs, DIY vending, history), Dispense Methods, and Plans Id’s for plan identifiers used with products or the API.
How do API access, webhooks, and security work?
In Developer: manage your Api Key, Set Webhook URL, and open Api Documentation. In Security: Whitelist IP for API access and use Error Management for retries; use Log out to end your session. Some screens require the main owner account.