Missing data from recipe endpoint

Greetings, it’s superb that there is a recipe endpoint now.

I’ve finally gotten the time to start to implement it into my application now and I feel like there is one piece of data that is important that is missing. How many items are created from the recipe and what profession/source it originates from.

I do not see a reason why this is not a part of it. Could be in the form of this if it is not the same quantity all the time:

{
  ...,
  creates_item: {
    ...,
    minCount: 5,
    rate: 7.9
    maxCount: 10,
  }
}

or this for those who have a set number of created items per craft:

{
  ...,
  creates_item: {
    ...,
    count: 5
  }
}

There is no information about how many a recipe creates. Recipes like K’bab creates 5 items at rank 1, but the API does not indicate this in any way.

Just to be sure, I mapped out all the present keys in all the wow recipes and still. I can’t see anything giving any information about this.

Am I missing something?

Here you have the model I generated from all the recipes:

export interface Recipe {
    id: number;
    name: object | string;
    media: {
        id: number;
        key: {
            href: string;
        }
    };
    _links: {
        self: {
            href: string;
        }
    };
    reagents: {
        reagent: {
            id: number;
            key: {
                href: string;
            };
            name: object | string;
        };
        quantity: number;
    }[];
    crafted_item: {
        id: number;
        key: {
            href: string;
        };
        name: object | string;
    };
    description: object | string;
    rank: number;
    horde_crafted_item: {
        id: number;
        key: {
            href: string;
        };
        name: object | string;
    };
    alliance_crafted_item: {
        id: number;
        key: {
            href: string;
        };
        name: object | string;
    }
}
1 Like

Yeah, I double this problem because it makes all the data from recipe endpoint almost useless. It will be awesome if fix will coming up in foreseeable future.

By the way, having spell_id will be also great for this endpoint. Because it’s not correlated with recipe_id but it’s also a useful data.

2 Likes

We’re looking into adding a crafted_quantity field to recipes, along with a minimum and maximum quantity, if applicable. :slight_smile:

3 Likes

Fantastic! Good to know :slight_smile:

I assume that there will be some patch notes when this goes live as usual.

Would be great with profession id as well, as mentioned :slight_smile:

1 Like

There is also another problem, which is relevant to this issue with purchase_price field. For some vendor items it shows us «wrong» value.

For example:

  • crafted_item: 160400 (named Foo’saka)

purchase_price value of this item is equals to 2.5g, but the the point is, that vendor doesn’t sell one (x1) Foo’saka for 2.5g. It sells *x10 at once for 2.5g, so the real price is 0.25g.

I guess this minor problem could be solved the same, by adding another field to schema like, purchase_quantity: 10

1 Like

I noticed that this is implemented now. Thanks!
Not sure when it was tho :stuck_out_tongue:

1 Like