Multiple created_at fields in JSON output. Any way to limit this?


#1

Hello,

We are using Splunk to parse through our twitter feed that looks at key words but are having issues parsing out the the timestamp since there are many created_at fields in the JSON output. Is there a way to limit this to only show the current timestamp of when the tweet was sent? If not which timestamp should we care about?


#2

The API responds with structured data… if you’re consuming the data into a hashmap or similar structure, it should be obvious which objects the various fields belong to… There’s only one created_at field directly attached to a core tweet object, for example.