How are optional parameters passed in?

[Scott Chamberlain]

Hello, 

I am trying to use your API, but am having a bit of trouble. 

For GET requests, are the optional parameters appended to the URL as in http://stuff?date=xxxx or passed in with the -d flag?  Does the answer differ for POST requests? At least in the example, parameters were passed with the -d flag.

Also, the docs don't really say what the parameter date does. Does specifying a date mean that only data after that data are returned?

Thanks, Scott

[John Nunemaker]

For get requests you can just add them in the query string, correct. The date parameter means return results for that date only.

--
You received this message because you are subscribed to the Google Groups "Gauges API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gauges-api+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Scott Chamberlain]

Thanks! But the following two calls with different dates return the same thing for me. Am I formatting these calls incorrectly?

curl -H "X-Gauges-Token: <token>" https://secure.gaug.es/gauges/4efd83a6f5a1f5158a000004/traffic?date=2013-05-28

curl -H "X-Gauges-Token: <token>" https://secure.gaug.es/gauges/4efd83a6f5a1f5158a000004/traffic?date=2013-05-25

[John Nunemaker]

Can you provide the responses? Those look good. I am definitely not getting the exact same results for my gauges. 

Are you using curl directly or a library in some language?

[Scott Chamberlain]

Thanks for your help!

I am building an R library to wrap your API, so am calling it from within R (here: https://github.com/ropensci/rgauges).

However, those curl calls were done in my terminal and I inspected data and got the same results for both calls. I tried it with a few different accounts and gauges, and same results. I'll try to figure it out - probably something on my end. 

-S