🧪 Sandbox Environment

🔐 Test Credentials

Use these pre-provisioned accounts in the sandbox. Each account has different roles and data sets.

⚡ Quick Start

Get up and running in three steps:

Step 1 — Authenticate

BASHcurl -X POST https://www.solabill.com/api/v1/client/auth/login \
  -H "Content-Type: application/json" \
  -d '{
    "email": "sandbox-client@solabill.test",
    "password": "sandbox-pass-2026!"
  }'

# Response:
# {
#   "data": {
#     "token": "1|abc123...",
#     "user": { "name": "Sandbox Client", "email": "sandbox-client@solabill.test" },
#     "account": { "company_name": "Sandbox Corp", "status": "active" }
#   }
# }

Step 2 — Create an Invoice

BASHcurl -X POST https://www.solabill.com/api/v1/client/invoices \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "invoice_number": "INV-SANDBOX-001",
    "recipient_id": "0192:sandbox-buyer",
    "amount": 5250.00,
    "currency": "AED",
    "issue_date": "2026-02-12",
    "due_date": "2026-03-12"
  }'

# Response includes invoice ID and dispatched Peppol message

Step 3 — Check Message Status

BASHcurl https://www.solabill.com/api/v1/client/messages \
  -H "Authorization: Bearer YOUR_TOKEN"

# Returns paginated list of Peppol messages with delivery status

🧪 Test Scenarios

Cover these scenarios before going to production:

⚖️ Sandbox vs Production

📦 Sample Data

The sandbox comes pre-loaded with the following test data after each reset:

🔬 Interactive API Explorer

Try API calls directly from this page. Authorize with the test credentials above, then expand any endpoint to send requests.

✅ Pre-Production Checklist

Before switching from sandbox to production, verify all of the following:

• ☐
  Authentication flow — Login, token storage, refresh/re-login on 401, logout
• ☐
  Invoice creation — Valid payloads accepted (201), invalid payloads rejected (422)
• ☐
  Credit note creation — Linked to invoices, correct amounts and references
• ☐
  Participant management — Register, list, and delete participants
• ☐
  Message tracking — Poll message status and handle all lifecycle states
• ☐
  Pagination — Handle has_more, current_page, last_page correctly
• ☐
  Error handling — Parse error envelope (error.code, error.message, error.details)
• ☐
  Rate limit handling — Respect 429 responses and Retry-After header
• ☐
  Webhook verification — Validate HMAC signature, reject stale/duplicate events
• ☐
  Idempotency — No duplicate invoices/credit notes on retries
• ☐
  Request tracing — Log X-Request-Id header from responses for support tickets
• ☐
  Base URL swap — Update from sandbox URL to production URL in config (not hardcoded)