Skip to content
REST API
/
/
Remove changelog subscrib...

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

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

Add changelog subscribers

Request

Adds email addresses as changelog subscribers in bulk.

Subscribers will receive email notifications when new changelogs are published (if email notifications are enabled during publishing).

Request Body

  • emails - Array of email addresses to add (required, 1-1000 emails)
  • locale - Locale for the subscribers (optional, defaults to organization default)

Email Validation

  • Invalid email addresses are automatically filtered out
  • Emails are normalized (trimmed, lowercased)
  • Duplicate emails are deduplicated

Rate Limiting

This endpoint is rate limited to prevent abuse. If you need to import more subscribers, please contact support.

Response

Returns a confirmation with the count of processed emails:

{
  "object": "changelog_subscribers_import",
  "count": 150
}

Errors

  • 400 - Invalid request (empty emails array, too many emails)
  • 429 - Rate limit exceeded
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
emailsArray of strings(email)[ 1 .. 1000 ] itemsrequired

Array of email addresses to add as changelog subscribers

Example: ["john@example.com","jane@example.com"]
localestring

The locale for the subscribers. Defaults to organization default locale.

Enum"bn""bs""pt-BR""bg""ca""hr""cs""da""nl""en"
Example: "en"
curl -i -X POST \
  https://docs.featurebase.app/_mock/rest-api/v2/changelogs/subscribers \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'Featurebase-Version: 2026-01-01.nova' \
  -d '{
    "emails": [
      "john@example.com",
      "jane@example.com"
    ],
    "locale": "en"
  }'

Responses

Success

Bodyapplication/json
objectstringrequired

Object type identifier

Value"changelog_subscribers_import"
Example: "changelog_subscribers_import"
countnumberrequired

Number of email addresses processed

Example: 150
Response
application/json
{
  "object": "changelog_subscribers_import",
  "count": 150
}

Remove changelog subscribers

Request

Removes email addresses from changelog subscribers in bulk.

Removed subscribers will no longer receive email notifications when new changelogs are published.

Request Body

  • emails - Array of email addresses to remove (required, 1-1000 emails)

Email Handling

  • Emails that don't exist as subscribers are silently ignored
  • Emails are normalized (trimmed, lowercased) before matching

Response

Returns a confirmation with the count of processed emails:

{
  "object": "changelog_subscribers_removal",
  "count": 150
}

Errors

  • 400 - Invalid request (empty emails array, too many emails)
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
emailsArray of strings(email)[ 1 .. 1000 ] itemsrequired

Array of email addresses to remove from changelog subscribers

Example: ["john@example.com","jane@example.com"]
curl -i -X DELETE \
  https://docs.featurebase.app/_mock/rest-api/v2/changelogs/subscribers \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'Featurebase-Version: 2026-01-01.nova' \
  -d '{
    "emails": [
      "john@example.com",
      "jane@example.com"
    ]
  }'

Responses

Success

Bodyapplication/json
objectstringrequired

Object type identifier

Value"changelog_subscribers_removal"
Example: "changelog_subscribers_removal"
countnumberrequired

Number of email addresses processed

Example: 150
Response
application/json
{
  "object": "changelog_subscribers_removal",
  "count": 150
}

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