# Read.write.as API

**URL:** <https://discuss.write.as/t/read-write-as-api/492>\
**Category:** Platform\
**Created:** [March 26, 2019, 9:23pm UTC](https://discuss.write.as/t/read-write-as-api/492 "2019-03-26T21:23:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\
**Post date:** [March 27, 2019, 6:32pm UTC](https://discuss.write.as/t/read-write-as-api/492/2 "2019-03-27T18:32:20Z")

</div>

Yep, we have a minimal, experimental API in place right now. It’s basically just one endpoint:

> `GET https://read.write.as/api/posts`
> 
> Returns 100 most-recent Read Write.as posts, paginated.
> 
> _Optional parameters:_
> 
> | parameter | example value | use |
> | --- | --- | --- |
> | `skip` | 10 | Specifies the number of posts to skip, for implementing pagination. |

Data is returned in the same JSON structure as the Write.as API, including the data envelope, so it should be possible to reuse data structures from those client libraries.

Our goal in having this was to eventually create a Read Write.as mobile app, but with [Read.as](https://read.as) now we’ll likely end up building something larger / more generalized, so we don’t have any active plans to develop the API further. But if you want to share what you’d like to build, maybe we could support certain features you need.

---

_[View the full topic](https://discuss.write.as/t/read-write-as-api/492)._