API Reference
Rules schema
filter
Filter
Object containing filtering rules which will evaluate against context object. Filter can be an instance of 5 different filter types described below.
Filter Schema
type
group
Filter group will evaluate by applying a logical operation to the array of filters provided
filters
Filter[]
Array of filters
operator
enum(and
, or
)
Logical operation
Use this endpoint to get the list of enabled features for the user. The response will contain the list of features that are enabled for the user.
Context object has to be flattened and delimited by dots and provided as query parameters. Example:
context.company.id=42&context.user.id=99
Feature key - unique identifier of the feature which you can find in app.bucket.co Example:
new-order-created
Standard response format for successful API calls
Use this endpoint to get the list of all features evaluated for the user.
Context object has to be flattened and delimited by dots and provided as query parameters. Example:
context.company.id=42&context.user.id=99
Feature key - unique identifier of the feature which you can find in app.bucket.co Example:
new-order-created
Standard response format for successful API calls
Use this endpoint to send feature events to Bucket.
Represents an event related to feature flag evaluation
Feature key - unique identifier of the feature which you can find in app.bucket.co Example:
new-order-created
The version of the targeting rules. Every time when targeting rules are updated the version is incremented.
Context object has to be flattened and delimited by dots and provided as query parameters. Example:
context.company.id=42&context.user.id=99
The result of the evaluation
The results of evaluation for each of the rules
The fields that were missing in the context for successful evaluation
Standard response format for successful API calls
Use this endpoint when you want to send user attributes to Bucket. If the user does not exist, it will be created. This endpoint is also used whenever you construct bucket client in any of the SDKs.
Represents a user entity with their attributes and metadata
Unique identifier for the user
Additional attributes of the user
Timestamp associated with the user data
Standard response format for successful API calls
Use this endpoint when you want to send company attributes to Bucket. If the company does not exist, it will be created. You can also use this endpoint to assign user to a company by including the user ID. This endpoint is also used whenever you construct bucket client in any of the SDKs.
Represents a company entity with its attributes and associated user
Identifier for the user linked to the company
Unique identifier for the company
Additional attributes of the company
Timestamp associated with the company data
Standard response format for successful API calls
Use this endpoint when you want to send a tracking events to Bucket.
Represents a tracking event with associated user, company, and metadata
Identifier for the user initiating the event
The name of the generated event
Additional event-related attributes
Identifier for the company linked to the event
Timestamp associated with the event
Standard response format for successful API calls
Use this endpoint when you want to send feedback events to Bucket.
Represents user feedback data with associated context and metadata
Unique identifier for updating existing feedback
Identifier of the user providing feedback
Identifier of the company linked to the feedback
Identifier of the feedback prompt
Identifier of the feature the feedback is related to
Feature key - unique identifier of the feature which you can find in app.bucket.co Example:
new-order-created
In case the feedback is initiated by a prompt this will be the question which was asked
In case the feedback is initiated by a prompt this will be the question which was asked
The source of the feedback
The score of the feedback
The user's input
When the feedback was submitted
Standard response format for successful API calls
Use this endpoint when you want to send multiple events to Bucket.
A collection of different types of operations to be processed in bulk
A single item in a bulk operation request that can be of different types
Standard response format for successful API calls
Last updated
Was this helpful?