heilog.ch.Api

GetRecipesRequest

The following routes are available for this service:
GET	/recipe

**GetRecipesRequest** Parameters:
Name	Parameter	Data Type	Required
PageSize	query	int	No
Page	query	int	No
Property	query	string	No
IsAscending	query	bool	No
Customer	query	string	No
Indication	query	string	No
ChargeNr	query	string	No
IncludeHiddenRecipes	query	bool	No

**GetRecipesResponse** Parameters:
Name	Parameter	Data Type	Required
Recipes	form	List<RecipeOverviewDto>	No
TotalEntities	form	long	No
Page	form	int	No
PageSize	form	int	No
Property	form	string	No
IsAscending	form	bool	No

**RecipeOverviewDto** Parameters:
Name	Parameter	Data Type	Required
RecipeId	form	long	No
CreatedUtc	form	DateTime	No
Title	form	string	No
CustomerName	form	string	No
Illness	form	string	No
LegacyChargeNr	form	string	No
Signature	form	string	No
PharmacistId	form	long?	No
OwnerId	form	long	No
IsVisible	form	bool	No
RecipeState	form	RecipeState	No
CanPrintLabel	form	bool	No
HasProtocol	form	bool	No
Message	form	string	No

**RecipeState** Enum:
Name	Value
Draft	0
RecipeSentToPartner	1
Printed	2
UnusedPartnerRecipe	3

To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv

HTTP + JSV

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

GET /recipe HTTP/1.1 
Host: heidak-api.build.exanic.ch 
Accept: text/jsv

HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	recipes: 
	[
		{
			recipeId: 0,
			createdUtc: 0001-01-01,
			title: String,
			customerName: String,
			illness: String,
			legacyChargeNr: String,
			signature: String,
			pharmacistId: 0,
			ownerId: 0,
			isVisible: False,
			recipeState: 0,
			canPrintLabel: False,
			hasProtocol: False,
			message: String
		}
	],
	totalEntities: 0,
	page: 0,
	pageSize: 0,
	property: String,
	isAscending: False
}