Subsection & Classification
IRS subsection and classification values work together to describe an organization's tax-exempt category. CharityQuery treats them as a paired filter and returns them as a combined response object.
The subsection value identifies the broader exempt organization category, while classification further describes the organization type inside that category.
Because the useful meaning comes from the combination, CharityQuery requires both values when filtering and resolves them into one readable response field.
GET /charities?subsection=03&classification=2000GET /nearby?origin_zip=28403&subsection=03&classification=2000Providing only one of these values returns a validation_error.
Instead of returning subsection and classification as separate response fields, request subsection_classification.
"subsection_classification": {
"subsection": "03",
"classification": "2000",
"description": "Educational Organization"
}If either value is unavailable or the pair cannot be resolved, this field may return null.
GET /charities?fields=ein,name,subsection_classificationsubsection_classification is selectable as a response field, but it is not used for sorting.
You can sort by subsection or classification individually. The combined response field subsection_classification is not a sort field.
GET /charities?sortBy=subsection&sortDir=ascGET /charities?sortBy=classification&sortDir=desc{
"code": "validation_error",
"message": "Request validation failed.",
"reqId": "4aab7166-4b5b-49d9-a25f-f7db49768a2d",
"details": [
{
"path": "subsection",
"message": "subsection and classification must be provided together",
"zodCode": "custom"
},
{
"path": "classification",
"message": "subsection and classification must be provided together",
"zodCode": "custom"
}
]
}GET /metadata/subsection-classificationThis route is recommended when building dropdowns, comboboxes, or filters that need valid paired combinations.
Read Metadata & Codes →