Technical Docs
Ask or search…
K

Create Log Entry

Create a new meal log entry
Use the createMealLog mutation to create a new log entry for the logged-in user. This service is commonly used together with the autocomplete search.
Please note that depending on the mealType being logged a different combination of parameters will be required. Please review our Food Log Guide before starting.
This mutation will be soon deprecated. It is recommended to use addFoodLog mutation

Required Arguments

Argument
Required?
Type
Description
mealDatabaseId
True
String!
The databaseId of the meal being logged.
I.e. If you are logging a recipe, then mealType should be RECIPE and mealDatabaseId should be the databaseId of the recipe.
mealType
True
MealType!
Available options are RECIPE, MENU_ITEM, OWN_RECIPE, USDA_MEAL, and OWN_ITEM
mealTime
True
MealTime!
Available options are BREAKFAST, SNACK, LUNCH and DINNER
quantity
True
Float
The number of servings that is being logged
serving
False
Float!
Represents the index of the item in the servings object that is being logged.
Don't use this field if you are using thecustomServingEquivalent option.
customServingEquivalent
False
Float
If not using the serving field, then enter here the equivalent in grams that is being logged.
I.e. If a protein bar weighs 100 grams (1 serving) and you want to log 0.8 servings, then this value would be 80.
date
False
Date!
format YYYY-mm-dd
time
False
Time!
format HH:MM

Example

Creating a new log entry for a recipe that was consumed for dinner on a particular date and time.
Mutation
Response
mutation {
createMealLog(
mealType: RECIPE,
mealTime: DINNER,
mealDatabaseId: "a281aa17-e746-4780-b69b-b4c3597bb783",
customServingEquivalent: 122.53701305389404,
date: "2020-04-02",
quantity: 1,
time: "20:00"
) {
success
databaseId
}
}
{
"data":{
"createMealLog":{
"success":true,
"databaseId":"cf4b117c751911eaa4d692235651c382"
}
}
}