06-26-2023 07:11 AM - last edited on 06-26-2023 10:41 PM by rupeshah
I just set up a new Webex Developer Sandbox. We had been using a trial org from five years ago but it expired. Since I don't have any easy way to verify a domain, I added my test users as external users. My app uses get people by email address. That works fine for my admin users by email. It works fine for my external users by Id. But when I try to get people by email address using the email address of one of my external users, I get zero items returns.
For example, my external user Id request --
/people?id=xxx
Returns --
{"notFoundIds":[],"items":[{"id":"xxx","emails":["365test7@ttops.onmicrosoft.com"],"displayName":"365test7 TimeTradeDevWebex","nickName":"365test7","firstName":"365test7","lastName":"365test7","userName":"365test7@ttops.xxx.com","avatar":"https://avatar-prod-us-east-2.webexcontent.com/Avtr~V1~xxx-xxx","orgId":"xxx","created":"2019-10-07T16:17:07.562Z","lastModified":"2023-06-23T20:42:25.887Z","type":"person"}]}
But I I then try the by email --
/people?email=a365test7@ttops.xxx.com
I get an empty response --
{"notFoundIds":null,"items":[]}
Any idea what I could be doing wrong? Do I have something wrong with the way the external users are added?
Solved! Go to Solution.
06-28-2023 04:52 AM
the /people API was changed some time ago to block lookup by email for users who are not in the same org as the user who makes the request. External users in your org would also be liable to this.
Only lookup by personId is allowed in this case, hence why you're experiencing the behaviour you see. You can see this change mentioned in our API Changelog, dated July 20, 2022.
06-28-2023 06:16 AM
I believe I got the book meeting to work by adding webex meeting suite to the license for the user.
06-28-2023 04:52 AM
the /people API was changed some time ago to block lookup by email for users who are not in the same org as the user who makes the request. External users in your org would also be liable to this.
Only lookup by personId is allowed in this case, hence why you're experiencing the behaviour you see. You can see this change mentioned in our API Changelog, dated July 20, 2022.
06-28-2023 04:59 AM
Thanks for the reply. I guess I'll have to use local users. I was able to create a few when I got a test domain verified. They lookup successfully but booking is failing. I suppose I should open a new thread for that but I'll paste it here for the time being.
{
"hostEmail":"365test7@ttdemo.net",
"enabledAutoRecordMeeting": false,
"allowAnyUserToBeCoHost": false,
"title": "kk catdev private teams with ttdemo.net email address -- 1A",
"start": "2023-06-27T16:30:00",
"end": "2023-06-27T17:00:00",
"timezone": "America/New_York",
"sendEmail": "false"
}
404 Not Found Transfer-Encoding:chunked server:Redacted expires:0 vary:origin,access-control-request-method,access-control-request-headers,accept-encoding x-frame-options:DENY Connection:keep-alive proxyreceivedtime:1687875595401 strict-transport-security:max-age=63072000; includeSubDomains; preload pragma:no-cache Date:Tue, 27 Jun 2023 14:19:57 GMT via:1.1 linkerd set-cookie:trackingSessionID=611AC45425164DF8A83055983E956F70; Path=/; Secure; HttpOnly x-content-type-options:nosniff;nosniff request_site_url:localhost:8080 proxyresponse:1958 cache-control:no-cache, no-store, max-age=0, must-revalidate trackingid:ROUTER_649AF001-B9E2-01BB-0138-AC12DA680138;ROUTER_649AF001-B9E2-01BB-0138-AC12DA680138 Content-Type:application/json
{"message":"Cannot find the data","errors":[{"description":"Cannot find the data"}],"trackingId":"ROUTER_649AF001-B9E2-01BB-0138-AC12DA680138"}
06-27-2023 07:28 AM
Adding API tag.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide