All my API calls are giving `Unauthorized` #3014

bsaoptima · 2024-10-20T17:25:14Z

bsaoptima
Oct 20, 2024

Hi there,

I am Cloud hosting Umami and I am trying to access the API endpoints with my API key but it is literally impossible. I only get Unauthorized errors and since the documentation is not very clear on what the actual endpoints are and how to access them, can someone give me a simple example that works?

Here is request:
curl https://api.umami.is/v1/websites -H "Accept: application/json" -H "x-umami-api-key <key>"

Thank you!

bsaoptima · 2024-10-20T17:27:16Z

bsaoptima
Oct 20, 2024
Author

curl https://api.umami.is/v1/api/websites -H "Accept: application/json" -H "x-umami-api-key <key>"

This one will actually trigger some anti-virus and this the response from the terminal:
bash: /mingw64/bin/curl: Permission denied

3 replies

Kajeczko Oct 22, 2024

Missing colon, should be -H "x-umami-api-key: <key>". Also you can add -v to see what is going on.

bsaoptima Oct 23, 2024
Author

Thanks, silly mistake from my side but now I get an internal error from the servers. Should I just host it myself and skip this?

curl https://api.umami.is/v1/api/websites -H "Accept: application/json" -H "x-umami-api-key: <key>" -v
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 64:ff9b::4c4c:1516:443...
* Connected to api.umami.is (64:ff9b::4c4c:1516) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
*  CApath: none
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [15 bytes data]
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [2570 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=api.umami.is
*  start date: Aug 26 09:31:02 2024 GMT
*  expire date: Nov 24 09:31:01 2024 GMT
*  subjectAltName: host "api.umami.is" matched cert's "api.umami.is"
*  issuer: C=US; O=Let's Encrypt; CN=R11
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x183161720a0)
} [5 bytes data]
> GET /v1/api/websites HTTP/2
> Host: api.umami.is
> user-agent: curl/7.78.0
> accept: application/json
> x-umami-api-key: <key>
>
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [122 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
} [5 bytes data]
< HTTP/2 500
< accept-ranges: bytes
< access-control-allow-credentials: true
< access-control-allow-headers: *
< access-control-allow-methods: GET,DELETE,PATCH,POST,PUT
< access-control-allow-origin: *
< age: 2978585
< cache-control: public, max-age=0, must-revalidate
< content-disposition: inline; filename="500"
< content-type: text/html; charset=utf-8
< date: Wed, 23 Oct 2024 09:04:41 GMT
< etag: "7a0ad3489f04588beed8af8788103545"
< last-modified: Wed, 18 Sep 2024 21:41:36 GMT
< server: Vercel
< strict-transport-security: max-age=63072000
< x-matched-path: /500
< x-vercel-cache: HIT
< x-vercel-id: cdg1::h97d8-1729674281120-2f82f83e50f8
< content-length: 1995
<
{ [5 bytes data]
100  1995  100  1995    0     0   5525      0 --:--:-- --:--:-- --:--:--  5526<!DOCTYPE html><html><head><meta charSet="utf-8"/><meta name="viewport" content="width=device-width"/><title>500: Internal Server Error</title><meta name="next-head-count" content="3"/><noscript data-n-css=""></noscript><script defer="" nomodule="" src="/_next/static/chunks/polyfills-78c92fac7aa8fdd8.js"></script><script src="/_next/static/chunks/webpack-4e7214a60fad8e88.js" defer=""></script><script src="/_next/static/chunks/framework-e037b0586cd7ceec.js" defer=""></script><script src="/_next/static/chunks/main-842856ba81ca9a8a.js" defer=""></script><script src="/_next/static/chunks/pages/_app-aea6920bd27938ca.js" defer=""></script><script src="/_next/static/chunks/pages/_error-3986dd5834f581dc.js" defer=""></script><script src="/_next/static/hNhiIyWwczXOcIA0i0-hX/_buildManifest.js" defer=""></script><script src="/_next/static/hNhiIyWwczXOcIA0i0-hX/_ssgManifest.js" defer=""></script></head><body><div id="__next"><div style="font-family:system-ui,&quot;Segoe UI&quot;,Roboto,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;height:100vh;text-align:center;display:flex;flex-direction:column;align-items:center;justify-content:center"><div style="line-height:48px"><style>body{color:#000;background:#fff;margin:0}.next-error-h1{border-right:1px solid rgba(0,0,0,.3)}@media (prefers-color-scheme:dark){body{color:#fff;background:#000}.next-error-h1{border-right:1px solid rgba(255,255,255,.3)}}</style><h1 class="next-error-h1" style="display:inline-block;margin:0 20px 0 0;padding-right:23px;font-size:24px;font-weight:500;vertical-align:top">500</h1><div style="display:inline-block"><h2 style="font-size:14px;font-weight:400;line-height:28px">Internal Server Error<!-- -->.</h2></div></div></div></div><script id="__NEXT_DATA__" type="application/json">{"props":{"pageProps":{"statusCode":500}},"page":"/_error","query":{},"buildId":"hNhiIyWwczXOcIA0i0-hX","nextExport":true,"isFallback":false,"gip":true,"scriptLoader":[]}</script></body></html>
* Connection #0 to host api.umami.is left intact

Kajeczko Oct 23, 2024

Should be https://api.umami.is/v1/websites.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

All my API calls are giving `Unauthorized` #3014

{{title}}

Replies: 1 comment 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

All my API calls are giving Unauthorized #3014

bsaoptima Oct 20, 2024

Replies: 1 comment · 3 replies

bsaoptima Oct 20, 2024 Author

Kajeczko Oct 22, 2024

bsaoptima Oct 23, 2024 Author

Kajeczko Oct 23, 2024

All my API calls are giving `Unauthorized` #3014

bsaoptima
Oct 20, 2024

Replies: 1 comment 3 replies

bsaoptima
Oct 20, 2024
Author

bsaoptima Oct 23, 2024
Author