Skip to main content
Version: v3

SaaS

API Service for SaaS

📄️Get Location Wallet Balance

Fetch the wallet balance for a specific location. Returns a resource object with balance details. **Deprecated:** this operation has moved to the Blade Platform API (`GET /wallet/company/balance?locationId={locationId}`, or `GET /wallet/balance` with a Sub-Account token) and will be removed from the SaaS API in the next version. Response shapes are unchanged, but no tenant id appears in the path: the agency comes from the token and the sub-account moves to a query parameter. Use the `wallet.readonly` scope.

📄️Update Location Wallet Balance

Update the wallet balance or complimentary credit settings for a specific location. Supports partial updates via updateMask field (AIP-134 compliant). **Deprecated:** this operation has moved to the Blade Platform API (`POST /wallet/company/balance/complimentary-credits`) and will be removed from the SaaS API in the next version. Request and response shapes are unchanged except that `companyId` is resolved from the access token and `locationId` moves into the request body. Use an Agency access token carrying the `wallet.write` scope.

📄️List agency wallet transactions

Fetch paginated wallet transactions for an agency (company). Supports skip/limit pagination, date-range and charge-type filters, timezone normalization, and additional non-indexed filters in the request body. **Deprecated:** this operation has moved to the Blade Platform API (`POST /wallet/company/transactions`) and will be removed from the SaaS API in the next version. Request and response shapes are unchanged, but `companyId` is no longer part of the URL -- the agency is resolved from the access token. Use an Agency access token carrying the `wallet.readonly` scope.

📄️List location wallet transactions

Fetch paginated wallet transactions for a sub-account (location). Supports skip/limit pagination, date-range and charge-type filters, timezone normalization, and additional non-indexed filters in the request body. **Deprecated:** this operation has moved to the Blade Platform API (`POST /wallet/transactions`) and will be removed from the SaaS API in the next version. Request and response shapes are unchanged, but the `locationId` is no longer part of the URL -- the sub-account is resolved from the access token. Use the `wallet.readonly` scope.