Showing 3 ideas for tag "get"

Feature Requests

Add GET parameter for tables

There is a limit of 50 variables in a GET. So, I can understand, sort of, the need to limit, but many of your tables have more than 50 cells. For example: [ACSSF, B04001, 0006, , 7, 109 CELLS, , FIRST ANCESTRY REPORTED, Ancestry], has 109 cells, and if I want to get Estimates plus Margin of Errors I need to get 218 variables. So, why not accept a table number parameter instead? It would make the calls much easier and... more »


4 votes
4 up votes
0 down votes

API Technical Discussions

Population by Zip

Community Member kudos icon + Community member
Hoping someone can point me in the right direction. I'd like to query the population for a specific zip code. I'm hoping there's a way to do this without defining the two number state code in the query.

Here's what my current query looks like...[myKey]&get=P0010001&for=zip+code+tabulation+area:[myZipCode]&for=state:*";

This works perfectly when I define the Zip Code and... more »


2 votes
2 up votes
0 down votes

Bugs / Problems

"Get" argument for API call: is there a length limitation?

I have an API request where the get argument that works is "P0030001,P0030002,P0030003,P0030004". However, I wanted to get all available names in that concept, which in total is a list of 8 elements "P0030001,P0030002,P0030003,...P0030008".


This request fails with error "unknown variable 'P0030005,P0030006,P0030007,P0030008"


Is there a limit on the length for the GET argument?


1 vote
1 up votes
0 down votes