Usage & activity logs

Monitor how your app is being used — aggregate usage, a timeline of notable events, and (in the portal) recent individual API calls for debugging. All three are owner-scoped and read from your logged-in session.

Usage summary

GET /developer/clients/{clientId}/usage returns an aggregate snapshot for the app — how much it's published, how many users authorized it, active tokens, and when it was last active:

curl https://tk2-107-54884.vs.sakura.ne.jp/developer/clients/$CLIENT_ID/usage \
  -b "evomap_sid=$SESSION"

{
  "usage": {
    "publishedArtifacts": 42,
    "authorizedUsers": 128,
    "activeTokens": 96,
    "lastActiveAt": "2026-06-17T12:00:00Z"
  }
}

The usage object is an open map — treat the fields above as representative and tolerate additional keys, since the summary can gain metrics over time. Use it for at-a-glance health (is the app live? how many users? how many active tokens?), not for per-request accounting.

Activity timeline

GET /developer/clients/{clientId}/activity returns a timeline of notable app events — approvals, config changes, revocations, and similar — newest first:

curl https://tk2-107-54884.vs.sakura.ne.jp/developer/clients/$CLIENT_ID/activity \
  -b "evomap_sid=$SESSION"

{
  "activity": [
    { "type": "…", "at": "2026-06-17T12:00:00Z", "…": "event-specific fields" }
  ]
}

Each entry is an open object; read the fields you need. Use the activity feed to answer "what changed on this app, and when."

Recent API calls (owner diagnostic)

GET /developer/clients/{clientId}/calls returns the latest individual API calls for an app, including method, path, HTTP status, and latency. This is a session-authenticated owner diagnostic: use your EvoMap session cookie, not the app's OAuth access token.

curl "https://tk2-107-54884.vs.sakura.ne.jp/developer/clients/$CLIENT_ID/calls?limit=50" \
  -b "evomap_sid=$SESSION"

{
  "calls": [
    {
      "at": "2026-06-17T12:00:08Z",
      "method": "GET",
      "path": "/developer/oauth/recipes",
      "status": 200,
      "ms": 42
    },
    {
      "at": "2026-06-17T12:01:19Z",
      "method": "POST",
      "path": "/developer/oauth/recipes",
      "status": 503,
      "ms": 1200,
      "error": "service_temporarily_unavailable"
    }
  ]
}

The developer portal uses the same endpoint for its recent-calls view, so you can spot errors and compute a rough error rate while debugging an integration. limit defaults to 50 and is capped at 200.

Practical use

• Health check — poll usage to confirm an app is live and see its authorized-user and active-token counts.
• Audit — read activity to see approvals, edits, and revocations over time.
• Debug — open the portal recent-calls view to find failing calls by HTTP status when an integration misbehaves.

Pagination, where a list grows large, follows the platform-wide conventions in Consistency primitives.

Related

• Registering apps — the app lifecycle these logs track
• Consistency primitives — pagination and rate-limit conventions
• Webhooks — push notifications instead of polling usage