> For the complete documentation index, see [llms.txt](https://docs.fieldmotion.com/fieldmotion-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fieldmotion.com/fieldmotion-api-docs/scheduleofrates/_setpricebands.md).

# \_setPriceBands

Sets the values of Price Bands in a Schedule of Rates.

### Parameters

#### id

The ID of the Schedule of Rates.

#### val

An array of Price Band values which will be set to a Schedule of Rates.

### Example

```
FM_api('ScheduleOfRates_setPriceBands',[
    'id'=>'370015',
    'val'=>[
      '30007'=>'7',
      '30008'=>'100'
    ]
  ]
);
```

In this example, a Schedule of Rates with an ID of 370015 will have two Price Bands (IDs of 30007 and 30008), 30007 set to 7 and 30008 set to 100. 

### Result

#### On Success

```
{'ok':1}
```

#### On Failure

If the "id" parameter is not set or has a value less than 1:

```
{"error":"missing or invalid parameter: id"}
```

If the "id" parameter does not match the ID of an existing Schedule of Rates:

```
{"error":"schedule of rates does not exist"}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fieldmotion.com/fieldmotion-api-docs/scheduleofrates/_setpricebands.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.