Teething Problems?

41 views
Skip to first unread message

Wayan Colenso

unread,
Apr 9, 2021, 10:31:30 PM4/9/21
to apidev
Hi there, 

I am new here, thank you for the key and all the info you have provided for us. 

I have been having trouble getting my API configured. I am getting a 404 error in Postman running tests, and cannot connect the API to a no-code tool I am trying to use (AppGyver). 

I have been able to download the FTP files no problem, but am not able to get anything from the API at all - I have a CORS plug-in in my browser and am seeing a 404 message there too. I have tested other APIs and am not having any issues there so wondering if I missed something. 

If anyone could walk me through what my settings should be, or let me know if this is a CORS issue or security setting I could work through? 

Thanks so much for your help,
Wayan

Richard Saffell

unread,
Apr 17, 2021, 6:48:36 PM4/17/21
to apidev, w.co...@gmail.com
Wayan,

A 404 error probably means a basic issue with the URL - can you provide the URL you are using in your requests?  Are you trying to connect to the Test or Production environment?

Richard

Wayan Colenso

unread,
Apr 19, 2021, 6:00:28 PM4/19/21
to apidev, Richard Saffell, Wayan Colenso
  Hi Richard, 

Thank you for responding to my message. I was just copying the URLs from the info section - 


(and then adding endpoints and search parameters also from the info section - eg. public/animals/search/available/dogs/haspic?sort&id - I tried all sorts of combinations and very broad searches as well). I was trying to authenticate with the API key by both query parameters and header.  

I didn't think I needed the RG login with an account number since I wasn't provided it - Could that be the issue? If not, could you please confirm the correct URLs or if there are any CORS restrictions? 
Sorry for such a basic question - I know I must be missing something obvious but if you could just help get me started I would greatly appreciate it! :)

Thanks,
Wayan

Richard Saffell

unread,
Apr 19, 2021, 9:57:14 PM4/19/21
to apidev, w.co...@gmail.com, Richard Saffell
Wayan,

It sounds like you want to use the v5 API, and your Test URL looks good, but the production URL should be:


The URL you listed is the v2 API and doesn't have the same URL structure.

If you're having trouble with specific URLs you can paste some here and we can help you.  Just don't paste your API key here.

And on that note - we prefer the Authorization header for the API key.  Just a lot cleaner instead of it being "exposed" in the URLs.

Hope that helps!

Richard

Wayan Colenso

unread,
Apr 27, 2021, 1:54:21 PM4/27/21
to apidev, Richard Saffell, Wayan Colenso
Thanks for your help Richard, that seems to have done the trick! :) 

Reply all
Reply to author
Forward
0 new messages