WeTransact Platform API (1.0)
Manage your Microsoft commercial-marketplace business programmatically: read the subscriptions customers have bought, report metered usage, and reconcile what Microsoft recorded and paid.
Every request needs your API key in an x-api-key header. Generate one under Settings in your WeTransact portal and store it securely; it is shown once.
GET /api/v1.0/subscriptions HTTP/1.1
Host: <yoursubdomain>.wetransact.io
x-api-key: YOUR_API_KEYA missing or unknown key returns 401. See Getting started for the full setup, and the Metering integration guide if you bill on usage.
| Area | Endpoints | Use it for |
|---|---|---|
| Subscriptions | GET /subscriptions, GET /subscriptions/{subscriptionId}, activate, reject | read what customers bought, with their plans and metered dimensions; drive the fulfilment lifecycle |
| Usage reporting | POST /subscriptions/{subscriptionId}/actions/charge | report metered usage to Microsoft. This is a billing action: an accepted charge lands on the customer's Azure bill |
| Reconciliation | GET /usage, GET /financials | what Microsoft actually metered, per dimension per day, and the revenue and payout lines behind it |
| Products | GET /products, GET /products/{productId}, GET /products/bypartnercenterofferid/{partnerCenterOfferId} | your listings, plans and pricing |
| Leads and deals | GET /marketplaceleads, GET /dealregistration/findcompany | marketplace leads and deal-registration lookups |
- Versioning. Every path is prefixed
/api/v1.0. - Response casing. Response bodies use PascalCase property names (
MarketplaceSubscriptionId,Success). Error bodies returned before any record exists use lower-casemessageandretryable. - Times. ISO 8601, UTC. Dates that come from Microsoft's reports carry no time zone and should be read as UTC dates.
- Identifiers.
dimensionIdon the charge endpoint is the Partner Center dimension id, the same valueGET /subscriptions?includeMeters=truereturns asMeterId.
- Reads: 10 requests per 60 seconds per client. Cache where you can.
- Charges: 10 in flight at once, 5 more may queue; beyond that you get
429. Retry later with the sameeffectiveStartTime.
Microsoft accepts one usage event per subscription, dimension and hour, and so does this API. Send effectiveStartTime explicitly and reuse the same value when retrying: you get 200 if it landed now, or 409 if it had already landed, never a double charge. Every error body tells you whether a retry is safe. The Metering integration guide walks through the whole flow, including a sandbox you can exercise without touching a real customer's bill.
Questions: support@wetransact.io.