Chastity Tracker API v2 Documentation: Stats

🔐 Authentication

All API requests must be authenticated via https using a bearer token.

Usage

URL

https://www.chastitytracker.org

HEADER

GET /api/v2/stats.php HTTP/2
Host: www.chastitytracker.org
Authorization: Bearer {YOUR_API_TOKEN}


📌 Endpoint: GET /api/v2/stats.php

Returns public stats data for the user associated with the token.

Response Example

{
  "ok": true,
  "data": {
    "nick":"example",
    "profile_url":null,
    "locked":true,
    "current_lock_start":"2026-01-15 09:00:00 UTC",
    "scheduled_end":null,
    "current_lock_time":"17 days 3 hours 12 minutes",
    "total_locked_since":"1 months 2 days 4 hours",
    "since_date":"2026-01-01 00:00:00",
    "link_game":null,
    "last_full":"2026-01-15",
    "last_ruined":null,
    "last_ted":"2026-01-20",
    "last_milking":null
  },
  "meta":{"version":2}
}

Possible Fields

• nick: Public-facing username
• profile_url: Public profile URL (only if user visibility allows it)
• locked: true/false
• current_lock_start: UTC start date of current lock (if public and active)
• scheduled_end: UTC scheduled end date (if available)
• current_lock_time: Human-readable duration
• total_locked_since: Human-readable duration
• since_date: Date since total is calculated
• link_game: Link game URL (if available)
• last_full, last_ruined, last_ted, last_milking: Last orgasm dates (public only)

Status Codes

• 200 OK — Data returned successfully
• 401 Unauthorized — Invalid or missing token
• 405 Method Not Allowed — Wrong method
• 500 Internal Server Error — Server error

⚠️ Security Notes

• Tokens must be stored securely by third parties.
• Users can revoke or regenerate tokens at any time.
• Never share a user’s token or sensitive info.

📅 Changelog

• 2026-02-02: initial v2 release

To go back to documentation index click here.