account

Suggestion activity and active-user report

Edits shown, accepted and ignored, plus active-user counts (logged-in and anonymous), over a window of days. Send a non-empty JSON body (unlike /api/v1/reporting/api_usage this handler rejects an absent or empty {} body with 400); the window defaults to the last 6 days when a field is omitted.

post/api/v1/reporting/api_user_activity

Request

  • Base URL: https://api.sapling.ai
  • URL: https://api.sapling.ai/api/v1/reporting/api_user_activity
  • Auth: one of:
    • HTTP bearer
    • none

Request body

end_days_backinteger

Window end, in days before today.

keystring

Sapling API key. Required when no "Authorization: Bearer <key>" header is sent; when both are sent, the body key takes precedence over the header.

return_usageboolean

When true, a successful JSON-object response additionally carries "usage": {"characters": <n>} — the billable character count this request submitted (0 for unbilled requests; the 2.5x adjustment for logographic languages is included, so CJK requests report more than their raw length). Repeat texts inside the billing deduplication window are still counted here even though they are not re-charged, so the number is an upper bound on the final charge. Responses whose body is not a JSON object (e.g. bare-array response formats) cannot carry the field. An existing usage field (such as account/status or completion token usage) is preserved unchanged.

start_days_backinteger

Window start, in days before today.

Response

Activity summary.

edits_acceptedinteger
edits_ignoredinteger
edits_showninteger

Changes

No recorded changes to this operation across all 1 revision of this API.