New API Proposal - APIUserAccountSpendCount

[wanggz21]

New API Proposal - APIQueryTheNumberOfTimesAuserSpendsMoneyOnAnAccount
The service will provide the account opening、 cancellation and credit rating of the current ID based on the ID information.
Input:
1.ID type、ID number、ID name
Output:

1. The number of account opening 2.The number of account cancellation 3.Credit rating

[wanggz21]

I have submitted a new merge request #125 to fix the issue above. Please update it to the latest merge request。

[jgarciahospital]

Hello @wanggz21 ,

This API proposal has been marked as Frozen because it has not shown active progress. Specifically, one or more of the following conditions have been met:

• The proposal owner has been absent from 3 consecutive Working Group meetings,

• There has been no activity on this issue (comments, PRs, or updates) for at least 6 weeks, or

• The proposal was approved by the TSC but no onboarding tracker was created after 3 WG sessions.

As a result:

• This issue has been labeled frozen.

• Any related open Pull Requests have been closed.

• The proposal is moved to the Frozen Proposals section of the Working Group agenda and is excluded from active discussions.

👉 How to reactivate this proposal:

If you would like to resume progress, please:

1. Comment on this issue explicitly mentioning the proposal owner, and

2. Notify the API Backlog Working Group at least 1 week before the agenda of the next WG meeting is finalized.

Once reactivated, the proposal will return to the main agenda for discussion.

If no action is taken within 6 months, the proposal may be archived and closed permanently.

Thank you for your understanding and collaboration!

[albertoramosmonagas]

Hi @wanggz21,

Frozen process (what it is): In CAMARA, “Frozen” proposals are temporarily parked when evolution stalls. After 6 months of no material activity (e.g., no WG updates/comments, no YAML/impl progress, no validation steps), they become archive candidates.

How we got here: This proposal has remained inactive for ~6 months while in Frozen status, meeting the criteria for archiving.

Action required to keep it alive (do both before 25 Sep 2025):

1. Post a status update as a comment on the GitHub issue (scope, next steps, and ETA).
2. Notify the API Backlog WG (reply-all to this email or via WG channel).

If we receive no response before the next Backlog session on 25 Sep 2025, the proposal will be archived: the issue (and related PRs) will be closed, it will be removed from agenda/minutes, and moved to Archived Proposals.

Best regards,

[jgarciahospital]

Issue considered as "Frozen", will be closed until API owner re-activates.