I recently made a PR that introduced scheduled post functionality into the API. This is all now live on the crust server for testing. I wanted to make a post describing the new endpoints and bring them to the attention of app developers as early as possible to solicit feedback.

The basic thought process was to create new endpoints for scheduled posts because the schema was sufficiently different than the schema used for existing post endpoints, as well as it will make our development lives easier on the backend. There are five new endpoints introduced with this that mirror the primary endpoints for doing basic post actions...

New Endpoints

1. GET /post/scheduled - return the information for a single scheduled post from a given post id. Similar to GET /post
2. GET /post/scheduled/list - return a list of the user's scheduled posts. Similar to GET /post/list, but obviously much more constrained in scope.
3. POST /post/scheduled - create a new scheduled post. Similar to POST /post.
4. PUT /post/scheduled - edit an existing scheduled post. Similar to PUT /post.
5. POST /post/scheduled/delete - delete or restore a scheduled post. Similar to POST /post/delete.

You can check out the schema on crust's swagger page. Also feel free to do testing over on crust and let me know of any issues that come up. The easiest time to make changes is now, before this makes its way into a stable release.