TTWrite API: Follow Requests

This suite of APIs provides functionalities to manage follow requests on the TTWrite platform, including fetching, approving, and deleting (ignoring) requests.

---

1. Fetch Follow Requests

Endpoint URL

//ttwrite.4up.eu/mobile_api/follow_requests

Description

Retrieves a list of follow requests sent to the authenticated user.

Parameters

Field	Value	Remarks
user_id	integer	The unique identifier of the user whose follow requests are being fetched.
limit	integer	Optional. The number of results to return per request. Default is 20.
offset	integer	Optional. The starting point for the results. Used for pagination.

Example Usage

httpCopy codeGET //ttwrite.4up.eu/mobile_api/follow_requests?user_id=123&limit=10&offset=0

Notes

• Authentication is required to access this API.
• Pagination parameters (limit and offset) are optional but recommended for managing large result sets.

---

2. Approve Follow Requests

Endpoint URL

//ttwrite.4up.eu/mobile_api/accept_follow

Description

Approves a follow request for the authenticated user, allowing the requesting user to follow.

Parameters

Field	Value	Remarks
request_id	integer	The unique identifier of the follow request to approve.

Example Usage

httpCopy codePOST //ttwrite.4up.eu/mobile_api/accept_follow
Content-Type: application/json

{
  "request_id": 789
}

Notes

• Authentication is required to access this API.
• Ensure the request_id corresponds to a valid follow request.

---

3. Delete (Ignore) Follow Requests

Endpoint URL

//ttwrite.4up.eu/mobile_api/ignore_follow

Description

Deletes or ignores a follow request for the authenticated user.

Parameters

Field	Value	Remarks
request_id	integer	The unique identifier of the follow request to delete/ignore.

Example Usage

httpCopy codePOST //ttwrite.4up.eu/mobile_api/ignore_follow
Content-Type: application/json

{
  "request_id": 789
}

Notes

• Authentication is required to access this API.
• Ensure the request_id corresponds to a valid follow request.

---

Notes for All APIs

• All endpoints require user authentication.
• Ensure valid user_id and request_id values to avoid errors.
• Use the appropriate endpoint based on the desired action (fetching, approving, or deleting requests).