Native usage based billing is in early access
This feature is in early access. If you're interested in joining the early access program, join the waitlist. We'll reach out when there's capacity if you meet the program requirements.
{ "error": { "type": "request_error", "code": "usage_event_future_timestamp", "detail": "usage event occurred_at 2026-08-07T12:00:00Z is more than 24 hours in the future.", "documentation_url": "https://developer.paddle.com/errors/usage-events/usage_event_future_timestamp" }, "meta": { "request_id": "00000000-0000-0000-0000-000000000000" }}Details
- Status code
- 400
- Error code
-
usage_event_future_timestamp - Error message
- usage event occurred_at %s is more than 24 hours in the future.
Common causes
occurred_atis set to a time more than 24 hours ahead of now, which no legitimate usage event should be dated.- A clock skew or timezone conversion bug on your side generated a future timestamp.
Troubleshooting
- Send
occurred_atas the real UTC time the usage happened, not a future or scheduled time. - Check your system clock and timezone handling if this happens unexpectedly.