API v2 is down at all

Warcraft Logs
1

Got Bearer Access Token and can’t fetch data niether via Insomnia Client (GraphQL body type) or via CURL example

  • Preparing request to https://warcraftlogs/api/v2/user
  • Current time is 2020-08-28T09:32:36.796Z
  • Using libcurl/7.69.1-DEV OpenSSL/1.1.1d zlib/1.2.11 WinIDN libssh2/1.9.0_DEV nghttp2/1.40.0
  • Using default HTTP version
  • Disable timeout
  • Enable automatic URL encoding
  • Enable SSL validation
  • Enable cookie sending with jar of 0 cookies
  • Could not resolve host: warcraftlogs
  • Closing connection 16

Could not resolve host: warcraftlogs

2

The domain is warcraftlogs.com not just warcraftlogs.

3

ahaha, you are right
then somebody should fix the docs
https://www.warcraftlogs.com/api/docs

so but got new issue

  • Preparing request to Warcraft Logs - Combat Analysis for Warcraft
  • Current time is 2020-08-28T12:07:57.015Z
  • Using libcurl/7.69.1-DEV OpenSSL/1.1.1d zlib/1.2.11 WinIDN libssh2/1.9.0_DEV nghttp2/1.40.0
  • Using default HTTP version
  • Disable timeout
  • Enable automatic URL encoding
  • Enable SSL validation
  • Enable cookie sending with jar of 0 cookies
  • Trying 75.119.201.145:443…
  • Connected to warcraftlogs.com (75.119.201.145) port 443 (#25)
  • ALPN, offering h2
  • ALPN, offering http/1.1
  • successfully set certificate verify locations:
  • CAfile: C:\Users\Cheburek\AppData\Local\Temp\insomnia_2020.3.3\2017-09-20.pem
  • CApath: none
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.3 (OUT), TLS alert, unknown CA (560):
  • SSL certificate problem: self signed certificate
  • Closing connection 25

If disabling validating SSL Certification then got

< HTTP/1.1 404 Not Found
< Date: Fri, 28 Aug 2020 14:38:35 GMT
< Server: Apache
< Upgrade: h2
< Connection: Upgrade
< Last-Modified: Fri, 28 Aug 2020 04:38:05 GMT
< ETag: “360-5ade89e652540”
< Accept-Ranges: bytes
< Content-Length: 864
< Content-Type: text/html

4

Any thoughts?

5

API doesn’t seem to exist, at least not with the URLs (with added .com) provided in the documentation.

6

It’s www.warcraftlogs.com

7

Oh, the subdomain was missing too. Now it works, thanks.

8

It seems down for me, can you send the v2 link you’re using?