# Gaaah! Why Twitter why?! (API help!)

**URL:** <https://forum.kirupa.com/t/gaaah-why-twitter-why-api-help/301998>\
**Category:** Uncategorized\
**Created:** [December 19, 2009, 1:26am UTC](https://forum.kirupa.com/t/gaaah-why-twitter-why-api-help/301998 "2009-12-19T01:26:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/kirupa/original/3X/6/2/621e5c11736f46532526e61be85940af4230f3e5.png) [@system](https://forum.kirupa.com/u/system)\
**Post date:** [December 19, 2009, 1:26am UTC](https://forum.kirupa.com/t/gaaah-why-twitter-why-api-help/301998/1 "2009-12-19T01:26:12Z")

</div>

OK…for my other forums I coded a quick script (PHP (cURL) & jQuery). It’s a simple PHP script that reaches to my twitter XML file (?count=1) to get my latest tweet, then jQuery/AJAX reads the PHP file. Problem is, that I keep hitting Twitter’s _maximum request restriction_. One thing I’ve noticed is that when I directly access the feed (from my browser) it displays regardless of whether I’ve hit the maximum or not. I was wondering if, somehow, using the might and prowess of cURL, I could spoof a _direct access._ Any tips/ideas?

[CENTER]\*\*SO PLEASE, PLEASE, REPLY. Even if it’s useless!  
\*\*[/CENTER]