Lazack Boost Lazack Boost / api
Developer Reference

API Integration
Personal & Merchant

Manage two types of API keys – Personal for ordering social media services, and Merchant for collecting TZS payments via mobile money. Generate, copy, and revoke keys securely.

Personal: Balance, Services, Orders Merchant: Payments, Balance, Transactions Separate Keys
Base URL https://boostapi.lazackorganisation.my.id/api/v1
Quick Start
3 simple steps to get live
  1. Generate the correct API key for your use case: Personal for SMM orders or Merchant for payment collection.
  2. Copy the key and send it in the X-API-Key header on each request.
  3. Call /services or /merchant/balance to confirm the key works before building your app flow.
Use the same base URL for all requests: https://boostapi.lazackorganisation.my.id/api/v1.
Best Practices
secure & production-ready usage
  • Store keys on your backend only, never in browser code.
  • Use different keys for personal and merchant flows to avoid access mix-ups.
  • Always validate webhook payloads before updating payment or order status.
  • Check the balance or transaction records before creating critical operations.
Personal API Key
for SMM orders & account management
Use this key for /balance, /services, and /order endpoints.
No key
Generate a personal key
Merchant API Key
for payment collection & merchant stats
Use this key for /merchant/balance, /merchant/transactions, and /payments/initiate.
No key
Generate a merchant key
Available Endpoints
personal & merchant routes
GET /balance Personal TZS & USD balance Personal
GET /services List SMM services with pricing Personal
POST /order Place a new SMM order Personal
GET /merchant/balance Merchant TZS balance Merchant
GET /merchant/transactions List completed payments Merchant
POST /payments/initiate Create a payment request Merchant
Each endpoint requires the corresponding X-API-Key header. Personal and merchant keys are not interchangeable.
Code Examples
snippets for both key types
# ── Personal API (SMM) ── # Balance curl -X GET "https://boostapi.lazackorganisation.my.id/api/v1/balance" \ -H "X-API-Key: YOUR_PERSONAL_API_KEY" # Services curl -X GET "https://boostapi.lazackorganisation.my.id/api/v1/services" \ -H "X-API-Key: YOUR_PERSONAL_API_KEY" # Create Order curl -X POST "https://boostapi.lazackorganisation.my.id/api/v1/order" \ -H "X-API-Key: YOUR_PERSONAL_API_KEY" \ -H "Content-Type: application/json" \ -d '{"service_id":1,"username_or_link":"https://...","quantity":1000}'
# ── Merchant API (Payments) ── # Balance curl -X GET "https://boostapi.lazackorganisation.my.id/api/v1/merchant/balance" \ -H "X-API-Key: YOUR_MERCHANT_API_KEY" # Transactions curl -X GET "https://boostapi.lazackorganisation.my.id/api/v1/merchant/transactions" \ -H "X-API-Key: YOUR_MERCHANT_API_KEY" # Initiate Payment curl -X POST "https://boostapi.lazackorganisation.my.id/api/v1/payments/initiate" \ -H "X-API-Key: YOUR_MERCHANT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"amount":1000,"buyer_name":"John","buyer_phone":"0758868502","buyer_email":"buyer@example.com","webhook_url":"https://yourdomain.com/webhook"}'
# Personal endpoints curl -H "X-API-Key: YOUR_PERSONAL_KEY" "https://boostapi.lazackorganisation.my.id/api/v1/balance" # Merchant endpoints curl -H "X-API-Key: YOUR_MERCHANT_KEY" "https://boostapi.lazackorganisation.my.id/api/v1/merchant/balance"
...
...
...
API Playground
test both personal & merchant endpoints
Generate the relevant key above before testing. Personal and merchant keys work separately.
Personal
Merchant
Response
// awaiting request...