Chastity Tracker API Documentation: Insert orgasm(s)

🔐 Authentication

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

Generating a Token

• Users can generate a secure API token from their profile page.
• Tokens are shown only once and must be stored securely.
• Only hashed versions are stored on the server.

Usage

URL

https://www.chastitytracker.org

HEADER

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


📌 Endpoint: POST /api/orginsert.php

Insert a new orgasm(s). Requires a valid authentication token (with write permission) and parameter(s) via json body (underlined means mandatory).

Parameters

• inserto: 1
• date: YYYY-MM-DD
• public: 0/1 to make it public or not
• grantedby: string
• type: string (e.g. Stroke,Rub etc etc) max 50 characters
• number: integer (to insert more than one)
• mode: string (if not one of the following, T&D will be inserted)
  • full: 1
  • ruined: 1
  • milking: 1
  • dom: 1

Example Request

POST /api/orginsert.php HTTP/2
Host: www.chastitytracker.org
Authorization: Bearer {YOUR_API_TOKEN}
Content-Type: application/json

{
  "inserto":1,
  "date":"2025-05-28",
  "mode":"full",
  "public":1
}

Response

{
  "message": "Orgasm(s) inserted succesfully",
  "orgasms_id": [1234,1235,...]
}

Status Codes

• 201 Created — Session inserted
• 400 Bad Request — Missing or malformed input (an info about the error will be returned)
• 401 Unauthorized — Invalid or missing token
• 403 Forbidden — Missing authorization
• 500 Internal Server Error — Something went wrong server-side

⚠️ 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

• 2025-06-06: Initial public API version released

To go back to documentation index click here.