---
title: "New Budget"
method: POST
path: "/v2/budgets"
tags: ["Routes", "Budgets"]
---

# New Budget

`POST /v2/budgets`

This request creates a new Budget.

Parameter: locationID, Type: Int, Required?: Required, Description: The ID of the location this budget will belong to.
Parameter: name, Type: String, Required?: Required, Description: The title of this budget.
Parameter: awaitingAllowPOEdit, Type: Boolean, Required?: Required, Description: When POs belonging to this budget are in the "ready to receive" state, will they be editable?
Parameter: awaitingEmailSend, Type: Boolean, Required?: Required, Description: When POs belonging to this budget enter the "ready to receive" state, should the assignee(s) be emailed?
Parameter: awaitingAssignmentType, Type: Enum, Required?: Required, Description: What type ('user' or 'team') should we interpret the awaitingAssignment value as?
Parameter: awaitingAssignment, Type: Int or Array of Ints, Required?: Required, Description: When POs belonging to this budget enter the "ready to receive" state, who will they be assigned to? If awaitingAssignmentType is 'team' then this cannot be an array, and may only be one number.
Parameter: prEmailSend, Type: Boolean, Required?: Required, Description: When PO items are received on POs that belong to this budget in the "ready to receive" or "partially received" states, should we send email notification(s)?
Parameter: prAssignmentType, Type: Enum, Required?: Required, Description: What type ('user' or 'team') should we interpret the prAssignment value as?
Parameter: prAssignment, Type: Int or Array of Ints, Required?: Required, Description: When bills are generated for PO items on POs that belong to this budget, who should the bills be assigned to? If prAssignmentType is 'team' then this cannot be an array, and may only be one number.
Parameter: defaultBudget, Type: Object, Required?: Required, Description: An object containing Boolean flags for global, purchaseRequests, and minPartQtyPOs. Setting any of these flags to true will set the same value for any other budgets at this location to false (we cannot have two default budgets). All properties of this object are required. global: Should this be the default budget for this location? purchaseRequests: When purchase requests are created from tasks, should this be the default budget? minPartQtyPOs: When a PO is automatically created due to part quantity threshold, should this be the default budget?

## Request body

- object
  - `locationID` integer
  - `name` string
  - `awaitingAllowPOEdit` boolean
  - `awaitingEmailSend` boolean
  - `awaitingAssignmentType` string
  - `awaitingAssignment` integer
  - `prEmailSend` boolean
  - `prAssignmentType` string
  - `prAssignment` integer
  - `defaultBudget` object
    - `global` boolean
    - `purchaseRequests` boolean
    - `minPartQtyPOs` boolean

## Response `201`

New Budget

- object
  - `budgetID` integer

## Other responses

- `400` — The request was malformed — either invalid JSON syntax or a validation failure (missing required field, wrong type, etc.).
- `401` — No `Authorization` header was provided on the request.
- `403` — The supplied credentials are invalid, the customer account is inactive, or the credentials do not have permission to perform this action.
- `409` — The request conflicts with the current state of the resource (e.g. a uniqueness constraint or a referenced parent that is in the wrong state).
- `429` — The per-minute or per-hour rate limit for this credential and method has been exhausted. Inspect the `X-RateLimit-*` headers to determine when to retry.
- `500` — An unhandled server-side error. The body message is generic (`System unavailable...`) when the underlying cause is a database fault; otherwise it reflects the raised error.

---

[API](https://skmtc.net/limblecmms/apis/limble-api-v2.md) · [All operations](https://skmtc.net/limblecmms/apis/limble-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/limblecmms/limble-api-v2/revisions/20801e23f7f2/schema)