The behavior pattern applies to resources that carry out operations. These resources have generally no state of their own and only support the POST operation. They may be a nested resource of an entity or container resource, which they may affect. This is in stark contrast to the POST operation on container resources which only affects the resource itself and its nested resources. Indeed, behavior resources have great latitude in impacting the overall state of a system.
Some behavior resources support the GET operation to return a HTML form that can be used to fill in the arguments for the POST operation.
Behavior resources never have nested resources. They are always leaf terms of the servers resource tree.
A behavior resource has the following pattern:
| Verb | Resource | Meaning |
| GET | /resource | (optional) Retrieve a form to submit the arguments for the operation. |
| POST | /resource | Carry out an operation. |