Add Security to Watchlist by ID
Add a security to an existing watchlist by providing the security's internal ID
Last updated
Add a security to an existing watchlist by providing the security's internal ID
Last updated
This PUT endpoint enables you to add a specific security to a specific watchlist of the user whose id is provided in the request's path.
There are six required parameters that must be provided in the request:
Et-App-Key (header). This is the unique key of your app that identifies your app when communicating with our service. Contact your administrator to get this key.
Authorization (header). This is the authorization token from the very first .
API version (path). Unless necessary, leave it at "1.0".
userID (path). This is the ID of the user whose particular watchlist needs to be appended by a new security.
watchlistID (path). This is the internal identifier of the watchlist that needs to be appended by a new security. You can retrieve the list of a user's watchlists with .
securityID (path). This is the internal identifier if the security that needs to be added to the watchlist. You can find the ID of a particular security with .
Here's the final template for this API request:
In response to this API request, you'll receive a JSON file with the updated watchlist. In this sample request we added the Ford stock to the watchlist:
Here are some of the common mistakes that developers make when attempting to add a particular security to a specific watchlist.
If you specify the wrong Et-App-Key parameter or fail to include it in the header altogether, you'll get the following error:
The following article covers the syntax for this API request in detail.
Another common mistake when making this API request is specifying the ticker symbol of the added security instead of its internal ID — for this purpose, there's a . If you specify the security's ticker symbol in this request, you'll receive the 400 status code and the following error message: