Get usage history

GEThttps://api.poe.com/usage/points_history

Overview

Retrieve your usage history with detailed information about each API call.

Features:

  • Entries are fetched by creation time, descending (most recent first)
  • Pagination support via starting_after cursor
  • Data available for up to 30 days
  • Maximum 100 entries per request

Authentication

Send your Poe API key in the Authorization header:

Authorization: Bearer sk_test_51SAMPLEKEY

All requests must be made over HTTPS.

Parameters

NameLocationTypeRequiredDescription
limitqueryintegerOptionalNumber of entries to return (max 100, default 20) Min: 1 ยท Max: 100 ยท Default: 20
starting_afterquerystringOptionalPagination cursor - use the query_id from the last entry of a previous response

Responses

FieldTypeRequiredDescription
has_morebooleanOptionalWhether there are more entries available for pagination
lengthintegerOptionalNumber of entries in the current response
dataobject[]Optional
data[].creation_timeint64RequiredUnix timestamp in microseconds when the query was created
data[].bot_namestringRequiredName of the bot or model used
data[].query_idstringRequiredUnique identifier for the query (used for pagination)
data[].usage_type"API" | "Chat" | "Canvas App"RequiredDescriptor for where the points were used Allowed values: API, Chat, Canvas App
data[].cost_pointsintegerRequiredNumber of points consumed by this query

โŒ Error codes

HttpTypeDescription
401authentication_errorAuthentication failed Invalid API key

Best Practices

Use the starting_after cursor for pagination. The query_id from the last entry can be used to fetch the next page of results.

Implement pagination for large result sets:

  • Start with a reasonable limit (20-50 entries)
  • Use has_more to determine if more pages exist
  • Pass the last query_id as starting_after for next page
  • Data is available for 30 days

๐Ÿ” Callbacks & webhooks

No callbacks or webhooks are associated with this endpoint.