You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noting that @peetucket reports the curl command works for him. It looks like wos-api.clarivate.com resolves to multiple IP addresses so maybe I'm talking to one that works a bit differently?
$ host wos-api.clarivate.com
wos-api.clarivate.com is an alias for wos-api.prod1.prod.oneplatform.build.
wos-api.prod1.prod.oneplatform.build is an alias for api-pub.us-west-2.prod1.prod.oneplatform.build.
api-pub.us-west-2.prod1.prod.oneplatform.build is an alias for kongapi-prod-us-west-2.prod.sp.aws.clarivate.net.
kongapi-prod-us-west-2.prod.sp.aws.clarivate.net has address 44.225.8.221
kongapi-prod-us-west-2.prod.sp.aws.clarivate.net has address 35.155.244.135
kongapi-prod-us-west-2.prod.sp.aws.clarivate.net has address 44.228.82.11
Adding --verbose to the curl command highlights that I'm talking to 44.225.8.221:
* Host wos-api.clarivate.com:443 was resolved.
* IPv6: (none)
* IPv4: 44.225.8.221, 35.155.244.135, 44.228.82.11
* Trying 44.225.8.221:443...
* Connected to wos-api.clarivate.com (44.225.8.221) port 443
It appears that an API request can return an empty string instead of a JSON object.
Get the Web of Science API Key:
Then try this request for ORCID 280000-0002-3271-7861:
And notice you get no output, but that it's a 200 OK. Once we figure out a reason for this we should adjust the
rialto_airflow.harvester.wos
.We talked about emailing our contact at Clarivate to see if there is a reason that we are seeing this behavior. Otherwise this API route works fine.
The text was updated successfully, but these errors were encountered: