I’m currently trying to access the diffdock API but am running into an issue where I cannot authenticate using my access key.
Here is a short example for what I am trying:
$ curl "https://health.api.nvidia.com/v1/biology/mit/diffdock" -X POST -H "Authorization: Bearer nvapi-ADSA....[truncated]"
{"status":401,"title":"Unauthorized","detail":"Invalid JWT serialization: Missing dot delimiter(s)"}%
It seems like this endpoint is looking for a JWT, not an access token? Let me know if I’m doing anything wrong in accessing this endpoint, I’m trying to follow the instructions outlined here:
I also tried this via the instructions outlined here: NIM embedding model downloads but fails with auth error on startup - #6 by joe173
This also failed with the same JWT error.
I’m not sure what changed, but the exact same request now succeeds. Thank you for everyone that reviewed this issue, the DiffDock NIM API is working great!
Thanks for following up, and glad to hear that it’s now working!
It’s possible it was a transient auth issue. It’s also important to include full headers. In the DiffDock example on build.nvidia.com (diffdock model by mit | NVIDIA NIM ) this is done as follows:
authorization_header='Authorization: Bearer $API_KEY_REQUIRED_IF_EXECUTING_OUTSIDE_NGC'
accept_header='Accept: application/json'
content_type_header='Content-Type: application/json'
And included in the curl request as:
response=$(curl --silent --request POST \
--url "$invoke_url" \
--header "$authorization_header" \
--header "$accept_header" \
--header "$content_type_header" \
...
Please let us know if you run into any additional issues!
1 Like
system
Closed
November 22, 2024, 7:51pm
6
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.