Authenticating Partner Session...
Loading identity, ledger balance, and catalog pricing
Verify your email to unlock wholesale pricing
We sent a verification link to your email. Click it and this dashboard unlocks: live partner pricing, card top-ups, and ordering.
- 1 Open the email from
orders@bluservices.xyz(check spam if it is not there). - 2 Click the verification link — it expires in 30 minutes and only works once.
- 3 Log back in with a magic link and your catalog pricing is waiting.
Wrong address, or still stuck after verifying? Email orders@bluservices.xyz and we will sort it.
—
Live Partner Catalog
LOADINGOrder Activity
Orders placed here or over the API, newest first. Credentials are fetched only when you open a specific order, so the list never carries them.
| Order ID | Item | Qty | Total | Status | Date | Credentials |
|---|---|---|---|---|---|---|
| No orders yet. Anything you place here or over the API will show up in this list. | ||||||
API Integration Reference
VERSION 1.0
Wire Blu Services wholesale ordering into your own software, bot, or storefront. Every call
authenticates with your secret key as an HTTP Bearer token. Export it once as
BLU_API_KEY and the examples below run as written.
Base Endpoint URL
https://bluservices.xyz/api/partner/v11. Fetch the catalog at your rate
curl -X GET "https://bluservices.xyz/api/partner/v1/catalog" \
-H "Authorization: Bearer $BLU_API_KEY"2. Place a programmatic order
curl -X POST "https://bluservices.xyz/api/partner/v1/orders" \
-H "Authorization: Bearer $BLU_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"item_id": "crunchyroll_mega_fan_1m",
"quantity": 1,
"idempotency_key": "custom_unique_id_12345"
}'Reuse the same idempotency_key when retrying a request — the API
will not bill you twice for the same order.
3. Check identity and balance
curl -X GET "https://bluservices.xyz/api/partner/v1/me" \
-H "Authorization: Bearer $BLU_API_KEY"4. Fund the balance by card
curl -X POST "https://bluservices.xyz/api/partner/v1/balance/topup" \
-H "Authorization: Bearer $BLU_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "amount_cents": 2500 }'
# -> { "checkout_url": "https://checkout.stripe.com/...", "amount_cents": 2500 }
# Open checkout_url in a browser. Balance is credited the moment Stripe
# confirms payment, and GET /balance then reflects it.5. Order events (signed webhooks)
curl -X POST "https://bluservices.xyz/api/partner/v1/webhooks" \
-H "Authorization: Bearer $BLU_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "url": "https://your-app.example/blu-events" }'
# Returns a whsec_... signing secret once. Each delivery carries
# X-Blu-Event and X-Blu-Signature: sha256=.
# Events: order.fulfilled, order.failed, balance.credited