# Expense Categories

An Expense Category represents the type of expense that is being reported.
Expense categories have no attributes and consist of just their name
as a string. They can be changed by Account Administrators.

## Fetching a list of Expense Categories

 - [GET /expense_categories](https://developer.kantata.com/kantata/specification/expense-categories/get-expense-categories.md): This endpoint returns structured Expense Category objects.
As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the results array
and will be indexed by ID in the expense_categories top-level JSON key.
Please see our Response Format section for more information.

## Creating a new Expense Category

 - [POST /expense_categories](https://developer.kantata.com/kantata/specification/expense-categories/create-expense-category.md): This endpoint returns structured Expense Category objects.
As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the results array
and will be indexed by ID in the expense_categories top-level JSON key.
Please see our Response Format section for more information.

## Updating an existing Expense Category

 - [PUT /expense_categories/{id}](https://developer.kantata.com/kantata/specification/expense-categories/update-expense-category.md): This endpoint returns structured Expense Category objects.
As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the results array
and will be indexed by ID in the expense_categories top-level JSON key.
Please see our Response Format section for more information.

## Deleting an existing Expense Category

 - [DELETE /expense_categories/{id}](https://developer.kantata.com/kantata/specification/expense-categories/delete-expense-category.md): Deleting an expense category updates the deleted_at attribute to the current time. Deleted
expense categories are not included by default in the index action and can be retrieved by setting
only_active filter as false.


The response will contain no content and an HTTP 204 status code if the request was
successful, or a standard Kantata OX error message explaining why the object could not be deleted.