Skip to main content
POST
/
api
/
v2
/
update-of-note
Update OnlyFans Note
curl --request POST \
  --url https://onlyautomator.com/api/v2/update-of-note \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "fanId": "12345",
  "onlyFansNoteId": "of_note_789123",
  "content": "This note was created on OnlyFans platform."
}
'
{
  "status": "success",
  "data": {
    "id": "note_34c5d6e7-5678-9012-ijkl-456789abcdef",
    "fanId": "12345",
    "onlyFansNoteId": "of_note_789123",
    "content": "This note was created on OnlyFans platform.",
    "source": "onlyfans",
    "createdAt": "2023-03-15T14:23:45Z",
    "updatedAt": "2023-03-15T14:23:45Z"
  }
}
Updates or synchronizes a note directly from the OnlyFans platform to the OnlyAutomator CRM system.

Endpoint

POST /api/v2/update-of-note

Authentication

This endpoint requires authentication with a valid JWT token in the Authorization header.
This endpoint requires authentication via bearer token representing a valid user session managed by Supabase Auth (cookies).Testing Note: Due to the requirement for a live user session, this endpoint cannot be successfully tested directly using the ‘Send’ button in this documentation with a static token.To test:
  1. Call this endpoint from your web application after logging in.
  2. Use curl or a similar tool with a valid, current user JWT obtained from your browser’s session after logging in.
Retrieving JWT Token for Testing: To test endpoints requiring a user session with tools like curl, you need the JWT access token stored by Supabase Auth in your browser.
  1. Log in to your application normally in your browser.
  2. Open Developer Tools (usually F12).
  3. Go to the Application tab (it might be called Storage in Firefox).
  4. Under the Storage section, find Cookies and select your application’s domain (e.g., http://localhost:3000 or https://onlyautomator.com).
  5. Look for a cookie named similar to sb-access-token (the exact name might vary slightly based on Supabase configuration).
  6. Copy the entire value of this cookie. This is your Bearer token.
  7. Use this copied value in the Authorization: Bearer <your_copied_token> header for your curl or other API tool requests.
Note: This token has a limited lifetime and you’ll need to copy a fresh one after it expires.

Request Headers

Authorization
string
required
Bearer token for authentication. Format: Bearer YOUR_JWT_TOKEN
Content-Type
string
required
Must be set to application/json

Request Body

fanId
string
required
Unique identifier of the subscriber/fan
onlyFansNoteId
string
required
Original note identifier from the OnlyFans platform
content
string
required
Content of the note from OnlyFans

Response

status
string
Status of the request (success or error)
data
object
Note object that was created or updated
data.id
string
Unique identifier for the note in OnlyAutomator (UUID).
data.fanId
string
Unique identifier of the subscriber/fan this note is associated with.
data.userId
string
Unique identifier of the OnlyAutomator user who initiated the sync or owns this record.
data.onlyFansNoteId
string
Original note identifier from the OnlyFans platform (corresponds to external_id in DB if used).
data.content
string
Content of the note.
data.source
string
Source of the note, typically “onlyfans” for this endpoint.
data.type
string
Type or category of the note (e.g., “general”, “important”, nullable).
data.createdAt
string
ISO timestamp of when the note record was created in OnlyAutomator.
data.updatedAt
string
ISO timestamp of when the note record was last updated in OnlyAutomator.

200 Success

{
  "status": "success",
  "data": {
    "id": "note_uuid_34c5d6e7",
    "fanId": "fan_uuid_12345",
    "userId": "user_uuid_abcdef",
    "onlyFansNoteId": "of_note_789123",
    "content": "This note was created on OnlyFans platform.",
    "source": "onlyfans",
    "type": "general",
    "createdAt": "2023-03-15T14:23:45Z",
    "updatedAt": "2023-03-15T14:23:45Z"
  }
}

Authorizations

Authorization
string
header
required

Standard user JWT token for authentication.

Headers

Authorization
string
required

Bearer token for authentication (JWT)

Body

application/json
fanId
string
required

Unique identifier of the subscriber/fan

Example:

"12345"

onlyFansNoteId
string
required

Original note identifier from the OnlyFans platform

Example:

"of_note_789123"

content
string
required

Content of the note from OnlyFans

Example:

"This note was created on OnlyFans platform."

Response

Note synchronized successfully

status
string
Example:

"success"

data
object