Fetching twitter-text configuration through REST API?


So twitter-text 2.0 has that fancy JSON configuration format now and it sounds like it would be a perfect fit for including in, say, /1.1/help/configuration.json instead of hardcoding the ranges in my application. As far as I can see, no REST API includes this.

My idea here is that fetching them through the API would get me some more future-proofing, but that’s assuming the ranges change before some other implementation detail of the code does.

Is this a reasonable assumption? Has this been considered? Or should I just go ahead and assume these ranges are unlikely to change any time soon?



This is a good idea, but not something that we currently have plans to add to an API endpoint. You can assume that the configuration file available in the twitter-text distribution is the source of truth for those values at any given time.