# Device Recipes Actions Details on the various actions that can be performed on the Device Recipes resource, including the expected parameters and the potential responses. ##### Contents * [Get](#get) * [Post](#post)
## Get Returns the device recipes for an application ```ruby result = client.device_recipes.get(applicationId: my_application_id) puts result ``` #### Authentication The client must be configured with a valid api access token to call this action. The token must include at least one of the following scopes: all.Application, all.Application.read, all.Organization, all.Organization.read, all.User, all.User.read, deviceRecipes.*, or deviceRecipes.get. #### Available Parameters | Name | Type | Required | Description | Default | Example | | ---- | ---- | -------- | ----------- | ------- | ------- | | applicationId | string | Y | ID associated with the application | | 575ec8687ae143cd83dc4a97 | | sortField | string | N | Field to sort the results by. Accepted values are: name, id, creationDate, lastUpdated | name | name | | sortDirection | string | N | Direction to sort the results by. Accepted values are: asc, desc | asc | asc | | page | string | N | Which page of results to return | 0 | 0 | | perPage | string | N | How many items to return per page | 1000 | 10 | | filterField | string | N | Field to filter the results by. Blank or not provided means no filtering. Accepted values are: name | | name | | filter | string | N | Filter to apply against the filtered field. Supports globbing. Blank or not provided means no filtering. | | my * recipe | #### Successful Responses | Code | Type | Description | | ---- | ---- | ----------- | | 200 | [Device Recipes](_schemas.md#device-recipes) | Collection of device recipes | #### Error Responses | Code | Type | Description | | ---- | ---- | ----------- | | 400 | [Error](_schemas.md#error) | Error if malformed request | | 404 | [Error](_schemas.md#error) | Error if application was not found |
## Post Create a new device recipe for an application ```ruby result = client.device_recipes.post( applicationId: my_application_id, deviceRecipe: my_device_recipe) puts result ``` #### Authentication The client must be configured with a valid api access token to call this action. The token must include at least one of the following scopes: all.Application, all.Organization, all.User, deviceRecipes.*, or deviceRecipes.post. #### Available Parameters | Name | Type | Required | Description | Default | Example | | ---- | ---- | -------- | ----------- | ------- | ------- | | applicationId | string | Y | ID associated with the application | | 575ec8687ae143cd83dc4a97 | | deviceRecipe | [Device Recipe Post](_schemas.md#device-recipe-post) | Y | New device recipe information | | [Device Recipe Post Example](_schemas.md#device-recipe-post-example) | #### Successful Responses | Code | Type | Description | | ---- | ---- | ----------- | | 201 | [Device Recipe](_schemas.md#device-recipe) | Successfully created device recipe | #### Error Responses | Code | Type | Description | | ---- | ---- | ----------- | | 400 | [Error](_schemas.md#error) | Error if malformed request | | 404 | [Error](_schemas.md#error) | Error if application was not found |