Skip to main content
GET /v1/auth/login-history returns the sign-ins to your account, newest first. Each entry includes the IP address, the device, where the IP is located and, when something looks unusual, the reasons it was flagged. Use it to show your users a “recent activity” screen, or to check for logins you don’t recognise.

Environments

Request

API-key authentication works too. A team member sees their own logins, not the account owner’s.

Rate limit

You can call this endpoint 30 times per minute. After that you get 429 Too Many Requests. The Retry-After header tells you how many seconds to wait.

Response

Entry fields

Location

location describes the IP address, not the user’s exact position. Treat it as approximate: city-level results can be off, and VPNs and mobile networks often appear in a different city or country. location is null when:
  • the IP is private or reserved, such as 192.168.x.x or 10.x.x.x;
  • the location could not be looked up when the user signed in;
  • the entry was recorded before location lookups were added.

Flags

new_ip, new_device and new_country compare against all of the account’s earlier successful logins, not only the current page. They never appear on the account’s first login.

Errors