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:
- Call this endpoint from your web application after logging in.
- 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.
- Log in to your application normally in your browser.
- Open Developer Tools (usually F12).
- Go to the Application tab (it might be called Storage in Firefox).
- Under the Storage section, find Cookies and select your application’s domain (e.g.,
http://localhost:3000 or https://onlyautomator.com).
- Look for a cookie named similar to
sb-access-token (the exact name might vary slightly based on Supabase configuration).
- Copy the entire value of this cookie. This is your Bearer token.
- 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.
Bearer token for authentication. Format: Bearer YOUR_JWT_TOKEN
Must be set to application/json
Request Body
Unique identifier of the subscriber/fan
Original note identifier from the OnlyFans platform
Content of the note from OnlyFans
Response
Status of the request (success or error)
Note object that was created or updated
Unique identifier for the note in OnlyAutomator (UUID).
Unique identifier of the subscriber/fan this note is associated with.
Unique identifier of the OnlyAutomator user who initiated the sync or owns this record.
Original note identifier from the OnlyFans platform (corresponds to external_id in DB if used).
Source of the note, typically “onlyfans” for this endpoint.
Type or category of the note (e.g., “general”, “important”, nullable).
ISO timestamp of when the note record was created in OnlyAutomator.
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"
}
}
Standard user JWT token for authentication.
Bearer token for authentication (JWT)
Unique identifier of the subscriber/fan
Original note identifier from the OnlyFans platform
Content of the note from OnlyFans
Example:"This note was created on OnlyFans platform."
Note synchronized successfully