fix(slack.com): replace admin-only spec with current scoped Web API (chat, conversations, users, canvases, bookmarks)

[elena-anagn]

Summary

The current slack.com/main/1.7.0 spec is Admin-API-only — all 50 operations are admin.*, so core methods like chat.postMessage, conversations.list, and auth.test are absent (see jentic-one-feedback #45). This adds 1.8.0, a scoped Slack Web API spec covering the everyday method families.

What's in 1.8.0

• 67 methods (51 POST + 16 GET) across chat (13), conversations (28), users (13), canvases (6), bookmarks (4), auth (3).
• GET read-methods modeled as query parameters; POST methods as application/x-www-form-urlencoded (+ application/json where documented) request bodies.
• Two security schemes: slackBearer (http/bearer — supports static xoxb-… tokens, the fix for Feature: Display Security Requirements in OpenAPI IO Extractor #45's second half) and slackOAuth (oauth2, 35 scopes).
• Includes post-2020 families (canvases.*, bookmarks.*) that no official Slack OpenAPI contains.

Provenance & method

Slack no longer publishes an official OpenAPI document — the last one (slackapi/slack-api-specs) is archived and frozen at 2020 (see jentic-one-feedback #46). This spec was generated from Slack's current documentation at docs.slack.dev/reference/methods (retrieved 2026-07-09) by parsing the per-method markdown pages; the generator is reproducible. Source recorded in info.x-jentic-source-url.

Validation

• Validates clean (oas-validate: 1 passing, 0 failing, 0 warnings).
• Live-tested against Slack: chat.postMessage → ok:true; conversations.list / bookmarks.list reachable and well-formed (return missing_scope, not unknown_method).

Requested action

Promote 1.8.0 as the current slack.com/main spec and retire the admin-only 1.7.0.

Note / follow-up

This is a scoped subset (67 of Slack's ~200+ methods) and intentionally omits the admin.* operations the old spec had. Those can be merged back in a follow-up if desired. Closes the spec half of #45.

🤖 Generated with Claude Code

[elena-anagn]

Why this PR exists — the backstory

This came out of dogfooding Jentic One, not a spec-cleanup pass. I was building a personal Design Digest — a scheduled routine that pulls design/product news each morning and pushes it to Notion + an email, brokered through Jentic One — and wanted to add a Slack notification as one of the channels.

That's where the trail started, and each step turned up something worth fixing:

1. Slack couldn't post at all. Importing slack.com and trying chat.postMessage failed — the directory's spec is Admin-API-only (50 admin.* ops, zero core Web API). Filed as jentic-one-feedback Feature: Display Security Requirements in OpenAPI IO Extractor #45.
2. No token option. The spec declared OAuth2-only, so Jentic's credential UI offered no Bearer-token path — even though Slack accepts static xoxb-… tokens. Second half of Feature: Display Security Requirements in OpenAPI IO Extractor #45.
3. The "official" fix was a fossil. The obvious source (slackapi/slack-api-specs) turned out to be archived and frozen at 2020, and Slack's live-hosted copy is the same stale v1.7.0. Slack no longer publishes any official OpenAPI. The current API lives only as HTML docs at docs.slack.dev.
4. The contribution guidance didn't cover this case. Following the repo's own agent instructions led straight to the stale spec — there's no guidance for "find the latest API, in whatever format, and generate an OpenAPI from it." Filed as jentic-one-feedback [AUTO] Import OpenAPI to Jentic Oak: #46.

So this PR is the end of that thread: a current Slack spec, generated from today's docs (reproducibly), with a bearer scheme so a token just works — fixing the concrete thing that blocked my digest.

The bigger point: we're hoping Jentic's users and the community will do exactly this — hit a gap, source the latest API, convert it, and contribute it back so the directory compounds in quality over time. This is us walking that loop ourselves, end to end, and fixing the potholes (#45, #46) we tripped on along the way so the next contributor doesn't.