A typo in a GQL field leads to an attempted lookup of a nonexistent JSON key. Update the schema and corresponding documentation.

Loving the API! I noticed scaling tiers were returning null from the GQL endpoint- looks like a little typo:

Request

# extra L in `scalling`, as defined in GQL schema
curl 'https://eldenring.fanapis.com/api/graphql' -H 'Content-Type: application/json' --data-binary '{"query":"{getWeapon(id:\"17f69d12746l0i1ojbzxzgz6gfjsi\"){name scalesWith{name scalling}}}"}'

Response

{"data":{"getWeapon":{"name":"Longbow","scalesWith":[{"name":"Str","scalling":null},{"name":"Dex","scalling":null}]}}}

Should be:

The knight Jerren's manchettes.

Jerren preferred a nomadic existence, but after spending time as a guest of the Carian royals, he became the guest commander for General Radahn. And for the first time, the restless tumbleweed would be bound by honorable oath.

Currently is:

Gauntlets of the Cleanrot Knights, celebrated for their undefeated campaign in the Shattering. The Cleanrot Knights vowed to fight alongside Malenia, despite the inevitable, if gradual, putrefaction of their flesh. Their acceptance of their fate made these battles fiercest of all.

There are plural and non plural versions of categories, ie: Greatsword and Greatswords , Dagger and Daggers. This makes using the category argument tricky due to having to handle both category arguments for one category type.

This is just looking at the "sorceries" request, but I wouldnt be shocked if it went further. So when looking at the array of "requires" it is too inconsistent to use as a source of sorting the overall fetch. we see that there are some which contain "intelligence" "faith" and "arcane" (ideal) while others will be missing some of the attributes or will have abbreviated the name (check out "Carian Slicer" requires [{"name": "Int", "amount": 14]) this is making it impossible to cater a list based on these nested arrays. Is there anyway to fix this across all fields (including weapons, incantations, ect?)

Thanks so much!

Getting this error: Expected Iterable, but did not find one for field \"Class.stats\"." The query thinks stats should return an array of ClassStats where the JSON is not set up as an array.

• Max limit increased to 100
• Added "Search" to all GraphQL objects
• added "total" in REST responses. This corresponds to the max amount of objects for that model
• Lots of improvements in data quality for "Armors" objects.
• Fix ashes of war REST route

Hello,

Thanks for this great API! I’ve sent you messages over Reddit but I have no ideas if you read those, so I’m making an issue here :) I’m making an iOS app using your GQL API, you can see it here: https://github.com/Dimillian/The-Roundtable Do you plan to add a search API? Would be wonderful. If you’re not planing to do it I can look into it. Also some kind of filter / sort would be great. For example being able to request weapons by scaling rank or armor by weight.

Thanks for this great API!

Here is some screens:

Hey, super cool API! I just started playing around with it a bit and noticed that the API doesn't return the total amount of possible data, which makes pagination a bit tricky. Could you add a field like total next to count, so people don't have to "brute force" check if there is more data available than initially requested?

Looking at some values from armor pieces, I could see all(?) values have been rounded down. E.g.: Black Dumpling Your values = dmgNegation: 2 3 2 2 3 3 3 3; resistance: 24 15 null 20 null Actual values = dmgNegation: 2.8, 3.1, 2.8, 2.8, 3.1, 3.4, 3.6, 3.1; resistance: 24 15 0 20 0

It would be awesome, if you could get more accurate numbers and maybe even replace the nulls with 0s.

• improved data quality
• added descriptions to all armors
• fixed class stats issue
• removed parenthesis from names (REST couldn't search)
• Fixed weight typo

Hi there. Great API and thanks for all the work putting this together!

I am trying to hit this API from the browser and getting a CORS pre-flight issue. Specifically:

405 Method Not Allowed

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://eldenring.fanapis.com/api/graphql. (Reason: CORS preflight response did not succeed). Status code: 405.

I do see in the Response Headers that you have access-control-allow-origin: * (which is correct if you intend to allow browsers to hit the API). But I also see there is an Allow header which is restricted to GET, POST. I believe this might be the problem.

Since you are using Next.js, I think we can just follow the example here to fix this.

I am happy to make a PR with these changes if you agree with the root cause and the suggestion solution. Please let me know. Thank you.

To improve data consistency, changed Phy20 to ("physical", 20), Phy40 to ("physical", 40) and Phy100 to ("physical", 100)

I was trying to obtain the levels assigned to the classes, but there is a misspelling on the words "inteligence" and "strenght" using graphql.

Noticed that all weapon stats appear to be pre-upgrade. It would be useful to see at least max upgrade stats so that weapons can be compared at that point.

Thanks.