For engineering teams reporting metered usage through the WeTransact external API and reconciling it against Microsoft's records. It covers the identifiers you join on, how to report usage so that retries are safe, every verdict Microsoft can give, how to read back usage and revenue, and how to use the sandbox.
| Sandbox | Production | |
|---|---|---|
| Base URL | https://wetx-api-sandbox.azurewebsites.net | https://<yoursubdomain>.wetransact.io |
| Authentication | x-api-key: <sandbox key from WeTransact> | x-api-key: <key generated under Settings> |
| Microsoft | Faked, stateful, fault-injectable | Real. Every accepted charge lands on your customer's Azure bill |
| Data | Two seeded subscriptions, seven days of usage history | Your tenant's subscriptions and reports |
A Postman collection with every request in this guide, including the sandbox fault scenarios, is available from WeTransact (External-API-Metering.postman_collection.json plus a sandbox environment file). Every request needs the x-api-key header; a missing key returns 401.
Wire format. Responses are JSON with PascalCase property names (MarketplaceSubscriptionId, Success, Microsoft.Status). Error bodies returned before a usage report exists use lower-case message and retryable.