API Documentation
logsapi gives developers programmatic access to social media logs. One API key authenticates every request: browse the catalog, place orders paid from your wallet, and read back orders and transactions.
Quickstart
- Sign up with GitHub or Google and confirm your email with the OTP we send you.
- Open API Keys in the dashboard and create a key.
- Copy the key. It is shown once and cannot be recovered.
- Fund your account from the Funding page. Orders are paid from this balance.
- Call
GET /api/productswith your key (see Authentication).
Base URL
https://logsapi.cvAll endpoints below are relative to this base. Use the apex domain exactly as shown — www.logsapi.cv redirects to https://logsapi.cv, so always copy the apex form into your code. If you are pointing at a different deployment, substitute its origin.
Migration notice
Balance and catalog responses now return only what you need. Provider balances, costs, and markups are no longer exposed. If you integrated before September 2026, update as follows:
| Before | Now |
|---|---|
GET /api/boosting/balance, /api/sms/balance, /api/sms/profile (provider USD) | Wallet balance in naira. Canonical: GET /api/balance. These three endpoints still return { "balance" } with a Deprecation header. |
basePrice, markup, cost, rate (upstream) | Use price (naira debited). Removed fields return undefined. |
charge, currency, provider, providerOrderId | Use orderId, status, amount, balance. Order status keeps status, remains, startCount. |
Endpoints
| Resource | Method | Description |
|---|---|---|
/api/products | GET | Priced product catalog with categories. |
/api/products/[id] | GET | Single product by id. |
/api/orders | POST | Place an order, paid from your wallet balance. |
/api/orders | GET | Your order history, newest first. |
/api/boosting/services | GET | Priced boosting services catalog. |
/api/boosting/orders | POST | Place a boosting order, paid from your wallet balance. |
/api/boosting/orders | GET | Your boosting order history, newest first. |
/api/boosting/orders/[id] | GET | Check the status of a boosting order. |
/api/boosting/refill | POST | Create a refill for a boosting order. |
/api/boosting/refill/[id] | GET | Check the status of a refill. |
/api/boosting/cancel | POST | Cancel one or more boosting orders. |
/api/boosting/balance | GET | Your wallet balance and currency. |
/api/sms/buy/activation/[country]/[operator]/[product] | GET | Rent a virtual number, paid from your wallet balance. |
/api/sms/check/[id] | GET | Poll an SMS order until the code arrives. |
/api/emails/plans | GET | List rentable email windows and available domains. |
/api/emails/rent | POST | Rent an email address, optionally branded with your name. |
/api/emails/inbox/[id] | GET | Poll a rental until the verification code arrives. |
/api/telegram/tiers | GET | List giftable Telegram Premium durations. |
/api/telegram/orders | POST | Buy a Premium gift and get its activation link. |
/api/transactions | GET | Wallet ledger with totals and running balance. |
/api/balance | GET | Current wallet balance as a single number. |
/api/blogs | GET | Published blog articles. Public, no key required. Supports ?q= search and ?limit=. |
/api/blogs/[slug] | GET | Single article by slug. Public. Add ?format=html for rendered HTML. |
Responses and errors
Successful requests return JSON with HTTP 200 (or 201 for order creation). Failures return JSON of the form { "error": "message" } with a meaningful status code. See the full list on the Errors page.