In Beta Phase
This feature is in the Beta phase. If you have any questions, ideas or suggestions please reach out to us at firstname.lastname@example.org.
The Update Tracker API updates a Tracker entity against the
trackerId which can be consumed in Symbl APIs.
Currently, the Tracker entities can be consumed in the Async APIs only. Support for other APIs will be added soon.
|No||DEPRECATED. The JWT token you get from our authentication process.|
The following request parameter (query-param) is accepted in the URI:
trackerId - The unique identifier of the Tracker to be updated.
|The name acts as a unique identifier assigned to the Tracker. It is case-sensitive, which means that a Tracker can be created with the same name but with different cases.|
|The vocabulary contains a set of phrases/keywords which signify the context of the Tracker. In other words, these are a set of sentences that are commonly used while talking about the said Tracker in different contexts.|
vocabulary cannot have duplicate phrases/keywords.
This API accepts a request body size up to 1MB. Sizes exceeding this limit will result in the error
413 - Request Entity Too Large.
This is the wrapper JSON Object which additionally also contains a unique
id associated with the Tracker entity that can be later used to instruct Symbl APIs to enhance tracking of the keywords/phrases in that conversation.
In case of unsuccessful responses, the following error codes will be returned from the API:
|The 409 response code specifies that the Tracker with that specific name already exists.||Modify the name of the Tracker or update the name of the existing Tracker with that name to resolve the error.|
|The 404 response code specifies that the Tracker with that specific ||Check the |
|The 429 response code specifies that the number of concurrent requests surpassed the limit for the API (which is 1 API call at a time).||Ensure that your system doesn’t make concurrent API calls that exceed this limit.|
|The 400 response code specifies that the request body or the parameters have incorrect key names or their values have types that are different than the ones expected.||Please read the message returned in the response to fix this error.|
|The 413 response code specifies that the size of the request body exceeds that of the maximum limit the API supports (which is 1 MB).||Please ensure that the size of the request body is under this limit to resolve this error.|
|The 502 response code specifies that the server failed to acknowledge the request. This may happen due to multiple reasons.||Please reach out to email@example.com if it persists even after multiple attempts.|
|The 504 response code specifies that the server failed to respond within the timeout duration.||Please reach out to firstname.lastname@example.org if it persists even after multiple attempts.|