# How we shipped a production API out of one Slack thread

DevFeed: [How we shipped a production API out of one Slack thread](<https://devfeed.tech/articles/how-we-shipped-a-production-api-out-of-one-slack-thread-16061.md>)

Original publisher: [Read original article](<https://workos.com/blog/shipping-a-production-api-from-one-slack-thread>)

Author: WorkOS

Published: 2026-08-27T14:09:14Z

Content type: article

Language: en

Sources: [WorkOS Blog](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [CRUD](<https://devfeed.tech/topics/crud.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [api](<https://devfeed.tech/tags/api.md>), [merge](<https://devfeed.tech/tags/merge.md>), [production](<https://devfeed.tech/tags/production.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [rest](<https://devfeed.tech/tags/rest.md>), [security](<https://devfeed.tech/tags/security.md>), [slack](<https://devfeed.tech/tags/slack.md>)

## AI overview

WorkOS describes how its IT Contact API was shipped from a single Slack thread. Humans made product and design decisions and gated the merge, while agents handled tickets, pull requests, review responses, and merges. The discussion shaped the API from an initial RPC proposal toward REST and resolved security, deletion, and duplicate-creation questions.

## Source excerpt

The WorkOS IT Contact API went live on August 18 out of a single Slack thread. Humans made the decisions and gated the merge; agents did everything else.