Preparation
- Log in to the AceDataCloud Platform.
- Create an account token in the Account Token Console.
- Regular users should use
user_id=me; you can also obtain your own UUID fromGET /api/v1/platform-tokens/me/.
API Overview
Regular users should pass
user_id=me. If it is not passed, the query is not first narrowed by account, and pagination may return 403 when encountering unauthorized objects; administrators can view the entire table without passing it.
Query Parameters
paid, disabled, expired, low_balance, and tag are currently not server-side filtering parameters. For balance alerts, retrieve the list and determine them on the client side based on each Application’s remaining_amount, service.unit, and business thresholds.
Request Examples
Response Description
The response is{count, items}. Each item contains Application model fields, with the following additional fields:
service:id,alias,title,type,unit,icon_url;credentials: credential summaries that the current caller is authorized to view;paid,remaining_amount,used_amount,disabled,allow_consume_global,allow_overdraft;- The actual value of
scopeisIndividualorGlobal; - The actual value of
typeisUsageorPeriod.
allow_overdraft is a read-only Boolean field controlled by administrators and defaults to false. For pay-as-you-go (Usage) applications with overdraft enabled, insufficient balance does not prevent calls, and charges are still based on actual usage; a negative balance indicates an amount pending settlement. Disabling, expiration, and API credential limits still take effect.
remaining_amount may be empty; the client must check for null before performing numeric comparisons. The quota unit is determined by service.unit.

