endpoint for new/upcoming shows?

This probably isn't coming to the free API any time soon, if ever. I would recommend using the "full schedule" endpoint, then manually filtering the episodes with both "season" and "number" set to 1. A little more work on your end, but the same result :)

I tried checking it out but the result is so big even my computer freezes when I try to copy it to a Json viewer so I can actually see what information it contains. I'm scared to imagine what it would do to a phone (I'm making an android app).

Is there a way to limit the number of results this endpoint returns? I feel like this endpoint should be paginated

The regular schedule endpoint is pretty much a "paginated" version :) Feel free to request a bunch of dates simultaneously and use that to create your overview.

how would i get a range of dates then? lets say i want to query for the schedule of an entire month. i tried doing http://api.tvmaze.com/schedule?country=US&date=2017-7 but i get {"name":"Unprocessable entity","message":"Not a valid ISO date","code":0,"status":422}
please dont tell me that i have to do it manually like this &date=2017-7-1&2017-7-2&2017-7-3&2017-7-4

Yes, you would do it by calling it on each day.

However it's going to be a lot quicker than the full one as you're only getting a month rather than all future episodes, and only from one country.

Oh no, I just meant you'd make seperate requests, one for each date. The first time your app launches you'd have to make a few requests (30, assuming you'd look one month ahead) but after that you'll only need one more request a day to catch up.

that doesn't really make sense... why would i make 30 separate requests? also that would hit the rate limit and i would get errors. it makes much more sense to enter a range of dates. but since that is not currently an option, i guess ill have to do it manually... even though it would effectively be a loop so it's not THAT much work, its still kind of annoying

I understand that this isn't the most optimal approach from the perspective of an API client. However, it makes a lot of sense from our side. We offer our API for free, while hosting definitely isn't free for us. We deal with hundreds of millions of API requests every week, so every tiny change can have a large impact on the resource usage and our hosting bill. The current schedule endpoint - one request for a single day - is easy to cache in various layers which reduces the load. An endpoint that accepts a range of dates would be much harder to cache thus much more costly.

That's the reason we can't offer this, nor some other frequently requested features like filters, sorting or similar endpoints where the response greatly varies based on user input. Not for free anyway, for users willing to pay for API access anything is possible. :)

thank you for your detailed explanation. although not exactly what i expected to hear, i completely understand.

in that case, may i please offer a compromise?
instead of adding a range of dates (which as you say can have many variations), will you consider adding an option for a specific month? for example: "http://api.tvmaze.com/schedule?country=US&date=2017-7" to retrieve the entire month of July 2017.
since the results will be limited to 1 month, its' size would also only vary so much... that way, its going to be a little easier for the clients, and should be easier for you to manage (although im not a server developer so i could wrong).

p.s.
for future posts... should new API feature request (such as this one) be posted in this forum or in Suggestions forum?

That could be an acceptable form if there's a lot of demand for it.

Both API bugs and suggestions are best placed here in the API forums.