Skip to content
REST API
/
/
Delete a comment

Featurebase API (2026-01-01.nova)

Welcome to the Featurebase API. This API allows you to programmatically interact with your Featurebase organization.

This documentation reflects API version 2026-01-01.nova.

Download OpenAPI description
index.json
index.yaml
Overview
URL
https://featurebase.app
License
Proprietary
Languages
Servers
Mock server
https://docs.featurebase.app/_mock/rest-api
Production
https://do.featurebase.app

API Versioning

This API uses date-based versioning. Each version is identified by a release date and slug, e.g., 2026-01-01.nova.

Specifying a Version

Include the version in the request header:

Featurebase-Version: 2026-01-01.nova

Or set a default version for your organization in the dashboard settings.

Version Compatibility

  • Newer versions may add new fields to responses (always backwards-compatible)
  • Breaking changes (removed/renamed fields, changed behavior) only occur in new versions
  • Your integration will continue to work as long as you pin to a specific version

Authentication

All API requests require authentication via API key.

Include in headers:

Authorization: Bearer <api-key>

Create and manage your API keys in the Featurebase dashboard.

Error Handling

The API uses conventional HTTP response codes to indicate success or failure:

  • 2xx - Success
  • 4xx - Client errors (bad request, unauthorized, not found, etc.)
  • 5xx - Server errors (internal error)

Error Response Format

All errors follow a consistent format:

{
  "error": {
    "type": "invalid_request_error",
    "code": "resource_not_found",
    "message": "Post not found",
    "param": "id",
    "status": 404
  }
}

Error Types

TypeDescription
authentication_errorAuthentication failed (401)
authorization_errorPermission denied (403)
invalid_request_errorInvalid request parameters or resource not found (400, 404, 410)
api_errorServer-side error (500)
rate_limit_errorToo many requests (429)

Boards

Boards (post categories) organize feedback into distinct containers with their own settings.

Operations

Posts

User-submitted feedback and feature requests. Posts belong to boards and can be upvoted, commented on, and tracked through statuses.

Operations

Post Statuses

Post statuses define the workflow stages for posts (e.g., In Review, Active, Completed).

Operations

Comments

Threaded discussions on posts and changelogs. Comments support voting, moderation, and privacy controls.

Operations

Delete a comment

Request

Deletes a comment by its unique identifier.

Deletion Behavior

  • Comments with replies: Soft delete

    • Content is replaced with "[deleted]"
    • Author information is anonymized
    • Comment remains visible to maintain conversation context
    • Votes and scores are reset to 0

  • Comments without replies: Hard delete

    • Comment is permanently removed from the database
    • All associated data is deleted

Permissions

  • Comment authors can delete their own comments
  • Admins can delete any comment (subject to permissions)
  • Lite seat admins can only delete their own comments
  • Non-authors require manage_comments or manage_comments_private permission

Response

Returns a deletion confirmation:

{
  "id": "507f1f77bcf86cd799439011",
  "object": "comment",
  "deleted": true
}

Errors

  • 400 - Invalid comment ID format
  • 403 - Not authorized to delete this comment
  • 404 - Comment not found or doesn't belong to your organization
Security
bearerAuth
Path
idstringrequired

Comment unique identifier

Example: 507f1f77bcf86cd799439011
Headers
Featurebase-Versionstring(FeaturebaseVersion)

API version for this request. Defaults to your organization's configured API version if not specified.

Example: 2026-01-01.nova
curl -i -X DELETE \
  https://docs.featurebase.app/_mock/rest-api/v2/comments/507f1f77bcf86cd799439011 \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Featurebase-Version: 2026-01-01.nova'

Responses

Success

Bodyapplication/json
idstringrequired

Unique identifier of the deleted comment

Example: "507f1f77bcf86cd799439011"
objectstringrequired

Object type identifier

Value"comment"
Example: "comment"
deletedbooleanrequired

Indicates the resource was deleted

Valuetrue
Example: true
Response
application/json
{
  "id": "507f1f77bcf86cd799439011",
  "object": "comment",
  "deleted": true
}

Delete a comment

Request

Deletes a comment using the legacy Clover API format.

This endpoint accepts the comment ID in the request body instead of the route parameter.

Request Body

{
  "id": "507f1f77bcf86cd799439011"
}

Deletion Behavior

  • Comments with replies: Soft delete

    • Content is replaced with "[deleted]"
    • Author information is anonymized
    • Comment remains visible to maintain conversation context
    • Votes and scores are reset to 0

  • Comments without replies: Hard delete

    • Comment is permanently removed from the database
    • All associated data is deleted

Permissions

  • Comment authors can delete their own comments
  • Admins can delete any comment (subject to permissions)
  • Lite seat admins can only delete their own comments
  • Non-authors require manage_comments or manage_comments_private permission

Response

Returns a success confirmation (Clover format):

{
  "success": true
}

Note: Nova API returns { id, object: "comment", deleted: true }, but Clover transformer converts it to { success: true } for backwards compatibility.

Errors

  • 400 - Invalid comment ID format or missing ID in body
  • 403 - Not authorized to delete this comment
  • 404 - Comment not found or doesn't belong to your organization
Security
bearerAuth
Headers
Featurebase-Versionstring(FeaturebaseVersion)

API version for this request. Defaults to your organization's configured API version if not specified.

Example: 2026-01-01.nova
Bodyapplication/json
idstringrequired

Comment ID

Example: "507f1f77bcf86cd799439011"
curl -i -X DELETE \
  https://docs.featurebase.app/_mock/rest-api/v2/comment \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'Featurebase-Version: 2026-01-01.nova' \
  -d '{
    "id": "507f1f77bcf86cd799439011"
  }'

Responses

Success

Bodyapplication/json
successbooleanrequired
Example: true
Response
application/json
{
  "success": true
}

Custom Fields

Configurable input fields for posts in your Featurebase organization. Custom fields allow you to collect additional structured data when users create posts.

Operations

Changelogs

Release notes and updates published by the organization. Changelogs keep users informed about new features, improvements, and fixes.

Operations

Admins

Team members who manage your Featurebase organization. Admins have roles that define their permissions.

Operations

Teams

Teams are groups within your Featurebase organization. Use this endpoint to list and retrieve team information for conversation assignment and organization management.

Operations

Brands

Brands represent distinct brand identities within your organization. Each brand can have its own help center and email sending address. Use this endpoint to list and retrieve brand information.

Operations

Contacts

Contacts are the customers and leads in your Featurebase organization. Use this endpoint to list and retrieve contact information.

Operations

Companies

Companies represent organizations or businesses that your users belong to. Use this endpoint to list and retrieve company information.

Operations

Surveys

Surveys allow you to collect targeted feedback from your users within your product. Surveys can be targeted to specific user segments or pages and can contain multiple questions with conditional logic.

Operations

Help Centers

Help centers allow organizations to create and manage knowledge bases with articles and collections. Currently, Featurebase supports one help center per organization.

Operations

Conversations

Conversations are messenger/inbox conversations in your Featurebase organization. Use this endpoint to list and retrieve conversation information.

Operations

Webhooks

Webhooks allow you to receive real-time HTTP callbacks when events occur in your Featurebase organization. Configure webhook endpoints to subscribe to specific event types.

Operations