Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On /users/{id}/badges, the description of the id parameter

a semicolon delimited list of user ids

diverges from the inferred standard for multi-valued parameters:

A single primary key identifier or a vectorized, semicolon-delimited list of identifiers.

Is this intentional and is there a difference in the way "list" parameters are handled vs "vectorized" parameters?

It is my understanding that "vectorized" means that constituent values must be sorted in ascending order. Is this correct?


Upon dumping all parameters I've come up with these variants:

id  string  A single primary key identifier or a vectorized, semicolon-delimited list of identifiers.
id  string  a semicolon delimited list of user ids
id  string  semi-colon delimited list of post ids

Can these all be treated similarly?


I got the answer I was looking for and am able to generate code that passes the following tests:

Tags (arbitrary number of strings):

public void CheckParamArrayTags()
    var client = new SoapiClient("", "");

    QuestionsTaggedByTagsResponse response = client.QuestionsTaggedByTags("sqlite", "sqlite3", "c#").GetResult();


            q => q.Tags.Contains("sqlite") && q.Tags.Contains("sqlite3") && q.Tags.Contains("c#")));

Ids (arbitrary number of int32)

public void CheckParamArrayId()

    var client = new SoapiClient("", "");

    UsersByIdResponse response = client.UsersById(242897, 1).GetResult();

    Assert.AreEqual(2, response.Users.Count);
    Assert.IsTrue(response.Users.Any(u => u.UserId == 1));
    Assert.IsTrue(response.Users.Any(u => u.UserId == 242897));
share|improve this question
up vote 1 down vote accepted

"Vectorized" does not imply anything about the order of its constituent components. The name comes from Vector Processors, a nicer name for the SIMD scheme.

The parameters are all treated identically, the documentation for each will be brought into sync on the next code push.

share|improve this answer
I seem to remember porting one of your unit tests that indicate that int.max;0 would return an error? – Sky Sanders Jun 6 '10 at 4:04
So, to generate param array factory methods I am going to key off of "semi[\s-]colon[\s-]delimited" - sound safe? – Sky Sanders Jun 6 '10 at 4:07
@code poet - Int32.MaxValue;0 would have returned a 404 error because nothing would have those 2 ids. I don't really follow your second question. – Kevin Montrose Jun 6 '10 at 4:12
I was asking if it would be future proof to use the presense of 'semicolon delimited', in any format, as an indication that an array is acceptable in the interest of generating methods with param array for ids and tags and such. – Sky Sanders Jun 6 '10 at 4:45
@code poet - yes, that will probably work; though I obviously can't make hard promises about the far future. If it works on the API as it stands now, it will almost certainly work for the v1 release however. – Kevin Montrose Jun 6 '10 at 6:18
perfect. that is all I would expect. – Sky Sanders Jun 6 '10 at 6:49
check the conclusion of this question for an explaination of the motivation. – Sky Sanders Jun 7 '10 at 2:52

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .