Mock1

The API doesn't support limiting the context of values returned. You would need to consume the whole list, parse the values (split at new line /r), and filter in your application.

The same is true for related issues, movies, characters, etc. You have to be able to consume the ENTIRE list, then limit on your end. For example, Wolverine has some 14,000+ Issue Appearances. You cannot get a response with anything between 0 and the full 14,000.

Ok, so new fun things:

• Power
  • It does not respect the fields_list; it always returns the list of characters; which makes the response unmanageable
• Volume
  • All relationship names are wrong in the documentation
    • characters instead of character_credits, etc.
  • Objects just returns Characters instead....

These Characters have mistakes in their Name. These problems are not visible in the UI, but can be seen in the API and affect the alphabetical sorting of Characters (even in the web UI, go sort Characters alphabetically and see what I mean). They need to be fixed in the database:

• Garth has a tab(/t) at the beginning of his name
• Kumiko Kitamura has a tab(/t) at the beginning of her name
• June XII has a space/whitespace at the beginning of his name (also, totally orphaned record)
• Thorn has a space/whitespace at the beginning of her name

This is also the case for story_arc as well

What are the odds that anyone from ComicVine even looks at this forum any more?

I have been consuming the API, and finding a lot of issues. Ranging from bad documentation (field names are not as documented, some are even misspelled - "count_of_isssue_appearances"), undocumented items (like series.episodes), to values always returning 0 (despite the CV UI showing a value, like team/story_arc.count_of_isssue_appearances), to blatantly wrong information being returned (movie.release_date returns the value for movie.date_updated).

Or that /search with story_arc as an entity returns zero results. It returns a number of found results, just no results.

I can adapt around bad documentation, just frustrating; but I can't work around bad data being returned. Movie.release_date is a major issue; not only is it the only way to tell some movies apart (like the two "Fantastic Four" movies), but it's giving a value that is just wrong. It took me a while to even realize this, as I assumed the info returned was correct. Now I check all the info returned by the API for each entity to understand what is reliable.

Is anyone actively caring about the API at this point? I can provide a list of issues I have found.

I feel like I am using this API about 3 years too late...