API server not connecting, redirecting to port 80?

Just signed up for a trial and was attempting to use the API. I am getting a connection timeout, so here is the output from CURL:

I inserted a space after https:// and http:// becuase as a new user it counted as too many “links”.

# curl --verbose --location 'https:// api.ordoro.com/product?limit=10&count=10&active=true' --header 'Authorization: Basic {{redacted}}'
*   Trying 44.227.171.243:443...
* Connected to api.ordoro.com (44.227.171.243) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: CN=api.ordoro.com
*  start date: Jan  8 00:00:00 2025 GMT
*  expire date: Feb  5 23:59:59 2026 GMT
*  subjectAltName: host "api.ordoro.com" matched cert's "api.ordoro.com"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M03
*  SSL certificate verify ok.
* TLSv1.2 (OUT), TLS header, Unknown (23):
> GET /product?limit=10&count=10&active=true HTTP/1.1
> Host: api.ordoro.com
> User-Agent: curl/7.76.1
> Accept: */*
> Authorization: Basic {{redacted}}
> 
* TLSv1.2 (IN), TLS header, Unknown (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 308 PERMANENT REDIRECT
< cache-control: no-cache,max-age=0,must-revalidate
< Content-Type: text/html; charset=utf-8
< Date: Tue, 28 Jan 2025 02:46:37 GMT
< Location: http://api.ordoro.com/product/?limit=10&count=10&active=true
< pragma: no-cache
< Server: gunicorn
< Strict-Transport-Security: max-age=31536000; includeSubDomains
< X-API-REQUEST-ID: a4c9c661-de1f-4f01-b1b4-12e837f2d94a
< X-Ordoro-API-Server: i-07fa33cede606fbc2 1.2267.0
< X-ORDORO-HANDLED-BY: ip-172-31-11-160
< Content-Length: 323
< Connection: keep-alive
< 
* Ignoring the response-body
* Connection #0 to host api.ordoro.com left intact
* Clear auth, redirects to port from 443 to 80Issue another request to this URL: 'http:// api.ordoro.com/product/?limit=10&count=10&active=true'
*   Trying 44.227.171.243:80...

I was missing the trailing slash. Very particular. :wink: Where can I find more information about the differences/etc between /v3/ and non-/v3/ routes/etc?

Adding the trailing / to /product solved the issue, need to find out more information about these differences in the /v3 and non-/v3 routes/etc…

Hey @scmsteve, welcome.

the difference between the two is pretty much named in the note in the introduction of the docs.

Note: Any routes with a /v3 designation will not allow for trailing slashes while all other routes and endpoints will require a trailing slash.

Glad you figured it out!