question

Upvotes
Accepted
18 1 2 5

No able to get an API key for PermID

I am going in circles trying to get a token for PermID. When I go to

https://developers.thomsonreuters.com/open-permid/open-permid-entity-search/dev-tools and click "Request a Key", I am asked to register. Entering e-mail, gives me "Your id has already been created, please sign in." Signing-In gets me back to the home page. From there I go to API the to "Entity Search" then to "Dev.Tools" and everything starts from the beginning... Is there anyway to get the token?

permid-apiintelligent-tagging-apiopen-permid-apitoken
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
Accepted
18 1 2 5

Hi @jirapongse.phuriphanvichai

Thank you very much for your reply.

Our IT say that out proxy server supports the TLS SSL protocol. Could you please let me know if you see anything wrong with the curl command I use, provided that token and proxy server address/port are correct?

I do not think it has anything to do with the proxy server. The same command but with "https://www.yahoo.com" as URL works fine.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

I have resolved it. It was a typo in the URL.

Upvotes
582 9 15 23

Hi @SIARHEI.VAURYNOVICH

If you'd already registered to "Request a Key", you should be able to login to PermID.org with your email and password. Once you'd login to PermID.org, you can click on "Display My Token" (to copy your Token) on the drop down menu under your user name.


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
18 1 2 5

Hi @susana.chang

Thank you very much for your help! For some reason, I am not able to use the API with the token. The error I get is:



$ curl -v --proxy-anyauth --proxy XXXX.XXX:1111 -X GET --header "Accept: application/json" "https://api.thompsonreuters.com/permid/search?access-token=XXXXXXXXXX&q=micro"
Note: Unnecessary use of -X or --request, GET is already inferred.
* STATE: INIT => CONNECT handle 0x6000578f0; line 1397 (connection #-5000)
* Added connection 0. The cache now contains 1 members
* Trying XXX.XXX.XXX.XXX...
* TCP_NODELAY set
* STATE: CONNECT => WAITCONNECT handle 0x6000578f0; line 1450 (connection #0)
* Connected to XXXX.XXX (XXX.XXX.XXX.XXX) port 1111 (#0)
* STATE: WAITCONNECT => WAITPROXYCONNECT handle 0x6000578f0; line 1557 (connection #0)
* Marked for [keep alive]: HTTP default
* Establish HTTP proxy tunnel to api.thompsonreuters.com:443
> CONNECT api.thompsonreuters.com:443 HTTP/1.1
> Host: api.thompsonreuters.com:443
> User-Agent: curl/7.50.3
> Proxy-Connection: Keep-Alive
>
* Read response immediately from proxy CONNECT
< HTTP/1.1 200 Connection established
<
* Proxy replied OK to CONNECT request
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* STATE: WAITPROXYCONNECT => SENDPROTOCONNECT handle 0x6000578f0; line 1544 (connection #0)
* STATE: SENDPROTOCONNECT => PROTOCONNECT handle 0x6000578f0; line 1571 (connection #0)
* Unknown SSL protocol error in connection to api.thompsonreuters.com:443
* Marked for [closure]: Failed HTTPS connection
* multi_done
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0
* The cache now contains 0 members
curl: (35) Unknown SSL protocol error in connection to api.thompsonreuters.com:443



Could you please let me know what I might be doing incorrectly?

Thank you very much,
Siarhei.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Hi @00000000

This is an example Curl command I tested with successful result (you can add the proxy params to it and it should work):

curl -v --header "X-AG-Access-Token:xxxxxxxxxxxxxxxx" https://api.thomsonreuters.com/permid/search?q=TRI
Upvotes
78.8k 249 52 74

It could be the problem in the proxy (XXXX.XXX:1111). If it works, the output will look like:

* Proxy replied OK to CONNECT request
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-SHA384
* ALPN, server did not agree to a protocol

The proxy server may not support the SSL protocol (TLS) used by Open PermID.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.