The question is not clear. Many API routes do allow arrays for inputs where such would make sense and is not too "expensive".
The plain /tags
route does not take arrays in its main parameter (inname
) because inname
performs a wildcard-ish search, and mixing the two would be too "costly", server-side.
But you can send an array of tags to the /tags/{tags}/info
route.
For example to get the number of questions for the oracle
, mysql
, and sql-server
tags you could call:
/2.2/tags/oracle;mysql;sql-server/info?site=stackoverflow&filter=!bNKX0pggz90UuM
which returns:
{
"count": 514139,
"name": "mysql"
}, {
"count": 229607,
"name": "sql-server"
}, {
"count": 96037,
"name": "oracle"
}
Important:
- Almost all array parameters to the API are separated by semicolons (
;
)
- Although you should be able to pass up to 100 tags in at a time, there is currently a bug that limits this. To be safe, pass in no more than 45 tags at a time for now.