No X-RateLimit headers!

[Luke]

Hi guys!

Thanks for the great API! After a little tweaking I managed to get it
to run flawlessly on my application! I just have a minor snag that
isn't particularly important, but it would be nice to have.

Calling the url: http://api.7digital.com/1.2/track/search with the
correct parameters through PHP cURL returns the XML and the headers.
Now I was reading through the documentation and I realise that I
should see some X-RateLimit headers, but they are not present. Here
are the only headers being returned:

HTTP/1.1 200 OK
Server: nginx/0.7.64
Date: Fri, 02 Jul 2010 14:31:49 GMT
Content-Type: text/xml; charset=utf-8
Connection: keep-alive
Cache-Control: private, max-age=86400
Content-Length: 10868
Last-Modified: Fri, 02 Jul 2010 14:32:04 GMT
x-7dig: p
Set-Cookie: SevenDigital.Web.Session=sid2=c485e126-d0df-4b87-
a342-46c88be46fd5&partner_34=1053; domain=.7digital.com; path=/
Set-Cookie: SevenDigital.Web.Session=sid2=c485e126-d0df-4b87-
a342-46c88be46fd5&partner_34=1053; domain=.7digital.com; path=/

Any help would be appreciated. I don't want to hit my limit without
knowing, as this could have a bad effect on my application if I cannot
incorporate a lock-down method.

[Hibri @ 7Digital]

Hi Luke,

If you don't get the headers, then you are not rate limited.
We are applying rate limits gradually.
Can you reply to me privately with your consumer key only, and I'll
check for you.

Hibri

On Jul 2, 3:41 pm, Luke <luke.zbih...@gmail.com> wrote:
> Hi guys!
>
> Thanks for the great API! After a little tweaking I managed to get it
> to run flawlessly on my application! I just have a minor snag that
> isn't particularly important, but it would be nice to have.
>

> Calling the url:http://api.7digital.com/1.2/track/searchwith the