Field Selection

Use the fields query parameter to request only the nonprofit data your application needs. Field selection keeps responses smaller, faster, and easier to work with.

How fields works
Pass a comma-separated list of field names in the fields query parameter.
GET /charities?fields=ein,name,ntee_group,asset_amount,ruling

Field selection is similar to choosing columns in a database query. Filters and sorting are still applied at the route level, even if the filtered or sorted field is not included in fields.

Supported routes
The fields parameter is available on the main nonprofit routes.
  • /charities
  • /charities/{ein}
  • /nearby

Most fields are shared across routes. The /nearby endpoint adds one extra field: distance_miles.

Basic example
Request only a few fields from the standard /charities endpoint.
GET /charities?state=NC&fields=ein,name,city,state,ntee_group&limit=2
{
  "page": 1,
  "limit": 2,
  "total": 143,
  "totalPages": 72,
  "next": 2,
  "prev": null,
  "charities": [
    {
      "ein": "030513435",
      "name": "Example Community Organization",
      "city": "Raleigh",
      "state": "NC",
      "ntee_group": {
        "code": "W",
        "description": "Public, Society Benefit"
      }
    }
  ]
}
Nearby-only distance field
Use distance_miles when searching from a ZIP code or latitude/longitude pair.
GET /nearby?origin_zip=28403&radius=25&fields=ein,name,city,state,distance_miles&limit=2
{
  "page": 1,
  "limit": 2,
  "total": 143,
  "totalPages": 72,
  "next": 2,
  "prev": null,
  "origin": {
      "lat": 34.2237,
      "lng": -77.8862,
      "source": "zip"
  },
  "charities": [
    {
      "ein": "020421110",
      "name": "Example Animal Rescue",
      "city": "Wilmington",
      "state": "NC",
      "distance_miles": 3.44
    }
  ]
}

distance_miles is only available on /nearby. It is not available on /charities because the standard route does not use a search origin.

Filtering + fields
Use filters to narrow the dataset, then fields to control the response shape.
GET /charities?city=Raleigh&state=NC&income_amount_gte=1000&income_amount_lte=10000&fields=ein,asset_amount,income_amount,revenue_amount&limit=2
{
  "page": 1,
  "limit": 2,
  "total": 10,
  "totalPages": 5,
  "next": 2,
  "prev": null,
  "charities": [
    {
      "ein": "020615760",
      "asset_amount": 278160,
      "income_amount": 195290,
      "revenue_amount": 195290
    },
    {
      "ein": "030547048",
      "asset_amount": 370668,
      "income_amount": 591904,
      "revenue_amount": 591904
    }
  ]
}
Single charity example
Use fields on an EIN lookup when you only need a few attributes.
GET /charities/020561076?fields=ein,name,deductibility,group,affiliation
{
  "charity": {
    "ein": "020561076",
    "name": "Marine Corps League",
    "deductibility": {
      "code": "1",
      "description": "Contributions are deductible"
    },
    "group": "0955",
    "affiliation": {
      "code": "9",
      "description": "Subordinate"
    }
  }
}
Enriched fields
Some selected fields return structured objects instead of raw codes.

Many IRS-coded fields return both the original code and a readable description.

"ntee_code": {
  "code": "D20",
  "description": "Animal Protection and Welfare"
}

Read the response format guide for the full list of enriched fields and special response shapes.

Read Response Format →
Selectable fields
These fields can be requested on /charities and /charities/{ein}.
  • ein
  • name
  • ico
  • street
  • city
  • state
  • zip
  • group
  • subsection_classification
  • affiliation
  • ruling
  • deductibility
  • foundation
  • activity
  • organization
  • status
  • tax_period
  • filing_req_code
  • pf_filing_req_code
  • account_paid
  • asset_amount
  • income_amount
  • revenue_amount
  • ntee_code
  • ntee_group
  • lat
  • lng
  • geocode_status

The /nearby endpoint supports these fields and adds distance_miles.

Next steps
Learn how fields connect to filtering, sorting, and response objects.