Update Project Content
Update the content of a specific project.
This endpoint allows you to update the content associated with a specific project.
Endpoint
POST https://rowlogy.com/api/:username/:projectSlug/content
Path Parameters
| Parameter | Type | Description |
|---|---|---|
username | string | The username of the project owner. Must start with "@". |
projectSlug | string | The project ID of the project. |
Authentication
You can authenticate your requests using one of the following methods:
Session Token
Include your session token in the Authorization header:
Authorization: Bearer <YOUR_SESSION_TOKEN>
API Key Authentication
Alternatively, you can authenticate using an API key. Include your API key in the Authorization header:
Authorization: Bearer <YOUR_API_KEY>
For more details on generating and managing API keys, see the Using API Keys guide.
Request Body
The request body should be a JSON object representing the new content for the project.
Example Request Body
{
"title": "My Updated Project",
"description": "This is the updated description of my project.",
"data": [
{
"id": 1,
"name": "Updated Item 1"
},
{
"id": 3,
"name": "New Item 3"
}
]
}Response
Success (200 OK)
Returns a success message upon successful update.
{
"message": "Project content updated successfully."
}For information on how to use the Rowlogy client libraries to interact with this API, please refer to the Client Libraries section.
Error Responses
- 400 Bad Request: If the request body is invalid.
- 401 Unauthorized:
- If no authentication (user session or API key) is provided.
- If the provided API key is invalid or expired.
- 403 Forbidden:
- If the authenticated user does not have write access to the project.
- If the API key used does not have the required permissions (e.g., write access) for this project.
- 404 Not Found: If the project or user does not exist.
- 500 Internal Server Error: For any server-side issues.