I have the case where I need to update other external systems like Notion or Gitlab issues/epics based on FeatureBase posts. When fetching a post I may or may not have an assignee property in the returned JSON payload representation of the post, which is further undocumented next to other properties that appear in the response that are also not mentioned in the Post model. I’ve tried to look up the user information for that user either via the Get single Identified user (
https://docs.featurebase.app/identify#identify-user) POST HTTP operation and sent a { “userId”: “<ID of assignee of fetched post>” } to the API. Ever since I get a generic "user" response for a user with nameUser and no e-mail address attached to it while I see the name, picture and what so ever in the FeatureBase Web UI perfectly. Your AI bot here on this page actually instructed me to use that operation as it was certain that the GET operation is not what I actually intended to call as it is only for “public” users not “internal” ones.
First, the current naming (and description) of those operations is IMO very misleading. Second, what is meant with Your own ID of the user? Do different user get different IDs for the same assigned user of a post? At least that’s what I’d interpret that sentence to be like. Third, if a text/plain content is sent to the POST endpoint, even when it includes f.e. something like the POST sample posted above, the API returns with a {"code":400,"message":"\"body\" must contain at least one of [email, userId]"} failure instead of pointing out that plain/text isn’t a supported media type.
Next, your Delete user API method is also questionable at best. As RFC 9110 (
https://www.rfc-editor.org/rfc/rfc9110.html#name-delete) points out, any payload sent with a DELETE request has no defined semantics and intermediary servers, caches or HTTP client frameworks may reject such opterations from working properly. I had to basically replace the HTTP client I’m using just to be able to send HTTP DELETE requests with a payload, if necessary.
How can I actually retrieve the email address of an assignee returned in a post response?
Log in to comment and vote
Comments2
Mar 22, 2024
PinnedHey @Rebekah Wilson,
The update is now live. :)
Check it out from this link: https://docs.featurebase.app/identify#query-identified-users
Roman Vottner
Nov 5, 2025
I have the case where I need to update other external systems like Notion or Gitlab issues/epics based on FeatureBase posts. When fetching a post I may or may not have an
assigneeproperty in the returned JSON payload representation of the post, which is further undocumented next to other properties that appear in the response that are also not mentioned in the Post model. I’ve tried to look up the user information for that user either via theGet single Identified user(https://docs.featurebase.app/identify#get-single-identified-user) GET HTTP operation, which returned a failure so far until I once requested the
Identify user(https://docs.featurebase.app/identify#identify-user) POST HTTP operation and sent a
{ “userId”: “<ID of assignee of fetched post>” }to the API. Ever since I get a generic "user" response for a user with nameUserand no e-mail address attached to it while I see the name, picture and what so ever in the FeatureBase Web UI perfectly. Your AI bot here on this page actually instructed me to use that operation as it was certain that the GET operation is not what I actually intended to call as it is only for “public” users not “internal” ones.First, the current naming (and description) of those operations is IMO very misleading. Second, what is meant with
Your own ID of the user? Do different user get different IDs for the same assigned user of a post? At least that’s what I’d interpret that sentence to be like. Third, if atext/plaincontent is sent to the POST endpoint, even when it includes f.e. something like the POST sample posted above, the API returns with a{"code":400,"message":"\"body\" must contain at least one of [email, userId]"}failure instead of pointing out thatplain/textisn’t a supported media type.Next, your
Delete userAPI method is also questionable at best. As RFC 9110 (https://www.rfc-editor.org/rfc/rfc9110.html#name-delete) points out, any payload sent with a
DELETErequest has no defined semantics and intermediary servers, caches or HTTP client frameworks may reject such opterations from working properly. I had to basically replace the HTTP client I’m using just to be able to send HTTP DELETE requests with a payload, if necessary.How can I actually retrieve the email address of an assignee returned in a post response?