Uh oh! We couldn’t find any match.
Please try other search keywords.
There are additional items for your
capsule.bxb file that need to be prepared for a public submission.
Ensure that each public submission version in your
capsule.bxb is unique and uses this format:
The capsule version must be a string with three numeric parts: "X.Y.Z". Each part must be an integer with no leading zeroes.
Bixby Developer Studio checks the version at submission time. If your capsule's version number already exists, the submission will fail with a
Capsule Version Check Failed error:
Aside from specifying targets, you can use marketplace constraints to further customize where your capsule is available when the Marketplace is available in specific countries.
By default, a capsule supports all markets. This optional step allows you to either allow or disallow specific countries (in ISO 3166-1 alpha-2 format) and device models (such as
A market is characterized by a country and a device model. For example,
SM-N960U:VZW is the code for a Galaxy Note 9 variant available through Verizon in the United States.
Your capsule can use
device-model-constraints to control which countries and device models, respectively, are supported. You can specify constraints using either
blocked-lists. Values within an
allowed-list are supported, and any values not explicitly listed are unsupported. The opposite is true for
blocked-list, where any values listed are unsupported, while values not listed are supported.
There is no direct relationship between
marketplace-constraints, you specify which users have access to use your capsule. However, with
targets, you specify the device type and language that is supported. If a capsule has target (
bixby-mobile-it-IT), for example, that means that users can talk to the capsule in Italian while on a mobile device. But
marketplace-constraints determine whether a user in Italy can actually use that capsule.
Within your capsule's
capsule.bxb file, you can specify either an
allow-list or a
block-list, and you can use valid regular expressions:
allow (SM-G965N) // S9+ Korean version
allow (SM-G960[A-Z]?) // any variant of S9
For details on specific keys, see the related reference documentation on
You must prepare a
capsule-info.bxb that provides information about your capsule, including the capsule name, website, and related branding images.
You must have a
capsule-info.bxb that is specific to each locale that your capsule supports. Place the file in the locale-specific
/resources/ folder. Example:
Here's an example of a capsule-info.bxb file:
companyName (Example, Inc.)
description (Example allows you to see examples of things.)
alias (Example Site)
Make sure you have values for the following keys:
privacy-policy-url- This is required only if you plan to ask the user to grant permissions to specific user-sensitive data.
The following keys are recommended, but not required:
Hints are used by Bixby to provide users with suggested queries. You can add suggestions within your capsule by creating a
hints.bxb file within your resources folder:
Here is an example
utterance (burn some toast)
utterance (fire up my space shuttle)
Your training and action implementations need to be able to handle these hints well.
Make sure you test your capsule with respect to the following:
Language: In addition to ensuring that your localized content is correct, you should check the following, for each language, in your
Ensure your capsule does not violate any of the capsule agreement policies. If your capsule is in violation, it will not be approved.
By submitting a capsule for the Marketplace, you agree to not violate any of the capsule agreement policies, including but not limited to the following:
capsule-info.bxbfile, if applicable.
capsule-info.bxbfile, if applicable.
dispatch-aliasesshould match the requirements and restrictions listed on the
The list of agreement policies is subject to change. If you are in violation of this agreement, the approval team will issue you an error report.