Each resource is assigned one and only one resource type. It's a way to group similar resources together for various scheduling and allocations purposes within your resource structure.

For example:

Resource Type: Conference Room

Resource: Conference Room 101
Resource: Conference Room 102
Resource: Conference Room 201
Resource: Conference Room 202
Resource: Conference Room 203
...

Resource Type: Pickup Truck

Resource: Truck 01
Resource: Truck 02
Resource: Truck 03
Resource: Truck 04
...

Resource types are the top-most general classification for resources. If your application has the need for swapping out or exchanging one resource for another, think of the resource type as a pool of resources that you can draw from in order to do this. aftonApi has additional ways of pooling and tagging resources in order to put together a variety of resource exchange scenarios, but we start with a single resource type to get things going.

After you have created at least one resource type and assigned at least one resource to it, you can now begin scheduling that resource using time spans.

GET	/resourcetype/{resourceTypeCode}	Gets a single Resource Type.
GET	/resourcetype/list	Gets a list of all active Resource Types.
POST	/resourcetype	Create Resource Type
POST	/resourcetype/{resourceTypeCode}	Update a Resource Type
DELETE	/resourcetype/{resourceTypeCode}	'Soft' delete a Resource Type

Basic Utility/Config Operations

POST	/resourcetype/{resourceTypeCode}/activate	Activate a Resource Type	Activates a Resource Type if it has been previously 'deleted'.
POST	/resourcetype/{resourceTypeCode}/pk	Modifies the primary key (resourceTypeCode) on a Resource Type	This is a safe operation with aftonApi. All entity relationships are preserved.