After opening its developer API to select companies for testing in March, Meta’s Twitter/X competitor Threads is now introducing developer documentation and a sign-up sheet for interested parties ahead of the API’s public launch, planned for June.

The new documentation details the API’s current limitations and its endpoints, among other things, which could help developers get started on their Threads-connected apps and any other projects that integrate with the new social network.

For instance, those who want to track analytics around Threads’ posts can use an Insights API to retrieve things like views, likes, replies, reposts, and quotes. There are also details on how to publish posts and media via the API, retrieve replies, and a series of troubleshooting tips.

The documentation indicates that Threads accounts are limited to 250 API-published posts within a 24-hour period and 1,000 replies — a measure to counteract spam or other excessive use. It also offers the image and video specifications for media uploaded with users’ posts and notes that Threads’ text post character counts have a hard limit of 500 characters — longer than old Twitter’s 280 characters, but far less than the 25,000 characters X offers to paid subscribers or the now 100,000 characters it permits in articles posted directly to its platform.

Whether or not Meta will ultimately favor certain kinds of apps over others remains to be seen.

So far, Threads API beta testers have included social tool makers like Sprinklr, Sprout Social, Social News Desk, Hootsuite, and tech news board Techmeme.

Although Threads has begun its integration with the wider fediverse — the network of interconnected social networking services that includes Mastodon and others — it doesn’t appear that fediverse sharing can be enabled or disabled through the API itself. Instead, users still have to visit their settings in the Threads app itself to publish to the fediverse.

Meta says the new documentation will be updated over time as it gathers feedback from developers. In addition, anyone interested in building with the new API and providing feedback can now request access via a sign-up page — something that could also help Meta to track the apps that are preparing to go live alongside the API’s public launch.