- Catalogue: look up one product or page through the product list, filtered by id, name, product code or category
- Provisioning: check a domain, then configure a Microsoft 365 subscription for a contract number with company and contact details
- Lifecycle: get, list and create subscriptions; change seat quantity and auto-renew; manage renewal; check transition eligibility and transition plans; suspend, unsuspend or cancel; follow provisioning stages
- Usage: current billing usage and month-by-month (YYYYMM) usage per subscription
- Customers: get, list and create trading customer records with company, tax and contact details
- 22 routes on whitelabel.bulutum.com plus a preproduction host for testing, documented in the AI integration guide (llms.txt)
Arena Bulutum Whitelabel API Connector
Arena Bilgisayar's Bulutum Whitelabel API for Microsoft 365 resellers — product catalogue, domain checks, subscription provisioning and lifecycle, billing usage and customer records — registered in Apivom Atlas as 22 routes and used with your own Bulutum login and AppKey.
What you can do
Use cases
- Provision a Microsoft 365 tenant for a new customer — Check the customer's domain, configure the subscription with their company and contact details, then follow the provisioning stages until the tenant is ready.
- Keep seats and renewals in step with the contract — Change seat quantity or auto-renew when headcount or terms change, and manage the renewal or move a subscription to another plan after checking transition eligibility.
- Reconcile billing against real usage — Read current and month-by-month usage for each subscription and compare it with what you invoice the customer.
- Subscription and customer inventory in the CRM — List subscriptions by status (waiting, active, suspended, cancelled) and trading customers next to the account record, so the reseller side is visible where the account is managed.
Bulutum is the whitelabel platform of Arena Bilgisayar through which resellers provision and manage Microsoft 365 subscriptions, and Apivom Atlas catalogues its API as 22 routes. Catalogue routes look products up by id, name, product code or category. Sales routes check a domain, configure a Microsoft 365 subscription for a contract number and run the subscription lifecycle: create, change seat quantity or auto-renew, manage renewal, transition between plans, suspend, unsuspend, cancel and check provisioning stages, plus current and monthly billing usage. Trading routes get, list and create customer records. Every route is a POST: the vendor wraps request bodies in a data envelope, adds page and pageSize for lists, and answers with data, hasFailed and messages. Atlas is a stateless pass-through here: the caller signs in at Bulutum for the Bearer token and sends it with the AppKey. The connector is newly registered and not yet verified live, and no Apivom product workflow uses it today, so it is available to resellers and distributors with workflows scoped per customer.
Authentication
Pass-through: you bring a Bulutum email and password and sign in at the vendor yourself for a 12-hour Bearer token, plus a static AppKey header on every call. Apivom Atlas stores and refreshes nothing — it routes and logs the call.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
How does authentication work, and does Atlas keep the token?
No. You sign in at Bulutum with your own email and password to get a Bearer token valid for 12 hours, then send it as the Authorization header together with the static AppKey header on every call. Atlas does not store or refresh the token, so your caller renews it before it expires.
Why is every route a POST, and what does a request look like?
Bulutum uses POST for reads too and wraps payloads: the body carries a data field (a filter object, or the contract number as a plain string on single-subscription routes) and page and pageSize on list routes. Responses return data, hasFailed and messages. Cancelling a subscription cannot be undone, so confirm before calling it.
Is there a test environment, and is the connector verified?
A preproduction host (preprodwhitelabel.bulutum.com) is registered as the test environment. The connector is newly registered and has not been verified live against Bulutum, so test the login and one catalogue lookup there before relying on it.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.