Typefully integration: operations for AI agents
Typefully connects to Type.com as an integration. This page lists the 24 operations documented for Claude and Codex in Type.com: 10 read, 8 write, 6 destructive.
About Typefully
Typefully API v2 reference operations, subject to Type setup and account permissions.
Categories: Marketing & Social
How to connect Typefully to Type.com
- Connect
- Configure provider-specific API target and authentication setup.
- Access
- Organization connection: one shared account for the workspace.
- MCP
- Selected social-publishing operations are not available through Type’s MCP server. Other operations remain available through MCP, subject to your connection’s permissions. These MCP restrictions do not apply within Type.
To add the connection, follow the steps in Space connections.
Documented operations
24 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
24 operations listed.
Users
- Read
Get current user
Retrieve the currently authenticated Typefully user associated with your API Key
GET /v2/me
Social Sets
- Read
List social sets
Retrieve all social sets (accounts) you can access. This includes accounts you own directly and accounts that belong to teams you are a member of.
GET /v2/social-sets - Read
Get social set details
Retrieve detailed information about a social set, including every configured social media platform (X, LinkedIn, Mastodon, Threads, Bluesky) with account details and profile information. **Required permission:** READ access to the social set.
GET /v2/social-sets/{social_set_id}/ - Read
Resolve LinkedIn organization from URL
Resolve a LinkedIn company/school URL into organization metadata that can be used to build LinkedIn mention syntax in post text. This endpoint is resolver-only and is not a general organization search endpoint. Mention format: `@[Company Name](urn:li:organization:123456)` **Required permission:** READ access to the social set.
GET /v2/social-sets/{social_set_id}/linkedin/organizations/resolve
Drafts
- Read
List drafts
Retrieve all drafts for a specific social set with optional filtering and sorting. Drafts are ordered by last edited date (most recent first) by default. **Draft statuses:** 'draft' = saved but not scheduled. 'scheduled' = queued to auto-publish at its scheduled_date. 'planned' = dated but inert: it has a scheduled_date but will NOT auto-publish until confirmed (by setting publish_at). A planned draft whose scheduled_date has passed is NOT overdue and NOT a failure - it simply hasn't been confirmed; replan it or confirm it. 'publishing' = a publish is in flight (transient). 'published' = successfully posted. 'error' = publishing failed. **Required permission:** READ access to this social set.
GET /v2/social-sets/{social_set_id}/drafts - Read
Get draft
Retrieve a specific draft by ID, including its content for all configured platforms, status, and scheduling information. If the draft has comment threads, the response includes Typefully comment-thread markers in `posts[*].text` and, for X Articles, in `platforms.x_article.content_markdown`. These markers are structural anchor metadata for `GET → modify → PATCH` round-trips; preserve them exactly when editing. For read-only display/export, pass `?exclude_comment_markers=true` to render draft text without markers. Content returned with that flag set should not be PATCHed back unless you intend to resolve or remove comment anchors. **Draft statuses:** 'draft' = saved but not scheduled. 'scheduled' = queued to auto-publish at its scheduled_date. 'planned' = dated but inert: it has a scheduled_date but will NOT auto-publish until confirmed (by setting publish_at). A planned draft whose scheduled_date has passed is NOT overdue and NOT a failure - it simply hasn't been confirmed; replan it or confirm it. 'publishing' = a publish is in flight (transient). 'published' = successfully posted. 'error' = publishing failed. **Required permission:** READ access to this social set.
GET /v2/social-sets/{social_set_id}/drafts/{draft_id} - Write
Create draft
Create a new draft with content for one or more social media platforms. The draft can be saved as a draft, planned (`plan_at`: dated but inert - it never auto-publishes until confirmed), scheduled for later publishing, or published immediately. **Account-level settings:** This endpoint automatically applies the following account-level settings if enabled: Auto-Retweet, Auto-Plug, and Natural Posting Time. **Required permission:** WRITE access to create drafts (planning included - it creates no publishing commitment). PUBLISH access is required to schedule or publish immediately.
POST /v2/social-sets/{social_set_id}/drafts - Destructive
Update draft
Update an existing draft with partial update semantics. Only provided fields are updated; omitted fields remain unchanged. Scheduled drafts require publish access to edit. ## Planning A planned draft is dated but inert: it has a `scheduled_date` but never auto-publishes until confirmed. Use `plan_at` and `publish_at` (mutually exclusive per request) to move a draft through the lifecycle: - `plan_at=<datetime|"next-free-slot">` on a plain draft plans it, on a planned draft moves the date (both write access), and on a scheduled draft unschedules it into a plan (publish access - it disarms a live schedule). - `publish_at=<datetime|"next-free-slot">` on a planned draft confirms it into a real schedule (publish access; echo the draft's `scheduled_date` to confirm at the planned date). `publish_at="now"` publishes it immediately. - An explicit `plan_at=null` or `publish_at=null` clears the date and returns the draft to plain draft status (write access from planned, publish access from scheduled). - Content edits on a planned draft require write access only. ## Note about Comment-thread markers If the draft has comment threads, submitted `posts[*].text` and X Article `platforms.x_article.content_markdown` must preserve the Typefully comment-thread markers received from `GET /drafts/{id}`. Validation is platform-level: every comment thread anchored on a platform must appear somewhere in that platform's submitted text. Recommended edit flow: GET the draft without `exclude_comment_markers`, modify text while preserving markers exactly, then PATCH with `force_overwrite_comments: false` (the default). - `409 COMMENTS_MARKER_MISMATCH` will be thrown if an expected comment thread marker is missing unless `"force_overwrite_comments": true` is set, in which case the affected threads are resolved server-side. - `400 COMMENTS_MARKER_UNKNOWN_ID` will be thrown if you submit an id that doesn't exist on this draft. - `400 COMMENTS_MARKER_MALFORMED` will be thrown if the marker tag is malformed (bad UUID, unbalanced, attribute violations, etc.). Pass `?exclude_comment_markers=true` to render the response text without markers (read-only / display rendering — does NOT skip server-side marker validation on the request body). Do not PATCH content returned with that flag unless you intend to resolve or remove comment anchors. **Required permission:** WRITE access to edit drafts. PUBLISH access is required to edit scheduled drafts, schedule, or publish.
PATCH /v2/social-sets/{social_set_id}/drafts/{draft_id} - Destructive
Delete draft
Delete a draft. Requires WRITE access. You can delete your own drafts in any status (DRAFT, ERROR, SCHEDULED, PUBLISHED, PUBLISHING) with WRITE access. Drafts created by other users also require WRITE access to delete. **Required permission:** WRITE access to this social set.
DELETE /v2/social-sets/{social_set_id}/drafts/{draft_id}
Media
- Read
Get media status
Retrieves the processing status of an uploaded media file. Poll this endpoint after uploading to check when the file is ready to use in drafts. If no file is received before the upload URL expires (1 hour), the media transitions to 'failed' — create a new media upload and try again. **Required permission:** READ access to the social set.
GET /v2/social-sets/{social_set_id}/media/{media_id} - Write
Create media upload
Generate a presigned S3 upload URL for images, videos, GIFs, or PDFs. After you receive the URL, upload the file contents with a PUT request and then reference the returned media_id when creating drafts. **Uploading:** Send a plain PUT with only raw file bytes as the body — no extra headers (`Content-Type`, `Authorization`, etc.). The presigned URL signature was calculated without them, so adding headers causes a `403 SignatureDoesNotMatch`. Use `curl -T <file>` (not `--data-binary`), `requests.put(url, data=file_bytes)` in Python, or `fetch(url, {method:'PUT', body:buffer})` in JS. A successful upload returns `200` or `204`. **Required permission:** WRITE access to the social set.
POST /v2/social-sets/{social_set_id}/media/upload - Write
Update media
Updates metadata of an uploaded media file. Currently supports setting or clearing `alt_text`. Alt text is copied into a draft when the media is attached (draft create or edit), so set it **before** referencing the media in a draft. To reliably change alt text on media already attached to a draft, update the media and then re-send the draft content with a draft PATCH. (Some platforms fall back to the media's current alt text when the draft snapshot has none, but only re-sending the draft content updates it everywhere.) **Required permission:** WRITE access to the social set.
PATCH /v2/social-sets/{social_set_id}/media/{media_id}
Tags
- Read
List tags
Retrieve all tags for a social set, ordered by their slugs. **Required permission:** READ access to the social set.
GET /v2/social-sets/{social_set_id}/tags - Write
Create tag
Create a new tag for a social set. The slug is automatically generated from the tag name, which must be unique per social set. **Required permission:** WRITE access to the social set.
POST /v2/social-sets/{social_set_id}/tags
Queue
- Read
Get queue
Retrieve queue slots and the scheduled AND planned drafts occupying them, between `start_date` and `end_date` (inclusive). Check each draft's `status`: 'scheduled' = will auto-publish at its `scheduled_date`; 'planned' = dated but inert - it will NOT auto-publish until confirmed (a past planned date is not overdue and not a failure). **Required permission:** READ access to this social set. Notes: - `start_date` and `end_date` are interpreted in the social set timezone. - Ranges larger than 62 days are rejected.
GET /v2/social-sets/{social_set_id}/queue - Write
Get queue schedule
Retrieve the queue schedule rules for a social set. **Required permission:** READ access to this social set. Behavior: - If the schedule row does not exist yet, it is created with defaults.
GET /v2/social-sets/{social_set_id}/queue/schedule - Destructive
Replace queue schedule
Replace the queue schedule rules for a social set. **Required permission:** ADMIN access to this social set. Semantics: full replacement (atomic). Rule validation: - `h` in `0..23`, `m` in `0..59` - `days` values are one of: `mon,tue,wed,thu,fri,sat,sun` - Duplicate day+time combinations are rejected Note: `rules=[]` is allowed and represents an empty schedule.
PUT /v2/social-sets/{social_set_id}/queue/schedule
Comments
- Read
List comment threads on a draft
Retrieve comment threads attached to a draft, ordered by creation time. Each thread includes the original `selected_text` snapshot and the full ordered list of comments. By default this endpoint returns only unresolved threads (`status=unresolved`). Use `status=resolved` to list resolved threads or `status=all` to list both unresolved and resolved threads. Example: `GET /v2/social-sets/4/drafts/12/comment-threads?status=all&limit=50`. **Required permission:** READ access to this social set.
GET /v2/social-sets/{social_set_id}/drafts/{draft_id}/comment-threads - Write
Create a comment thread
Create a new comment thread on a draft. A comment thread is the anchored discussion container; comments are the messages inside the thread. For post platforms (`x`, `linkedin`, `mastodon`, `threads`, `bluesky`, `substack`), provide `post_index` and anchor to a substring of that post's visible text using `selected_text`. Use `occurrence` to disambiguate when the same substring appears more than once; omit it to anchor on the first match. For X Articles, send `platform: "x_article"` and omit `post_index` (or use 0). `selected_text` matches commentable article text in document order; Markdown syntax, media tags, X post embed tags, and fenced-code text are ignored. Code blocks do not support comment anchors. X Article text comments cannot overlap existing stored X Article anchors; unsupported or overlapping selections return `400 VALIDATION_ERROR`. LinkedIn mentions appear in `posts[*].text` as `@[Name](urn:li:organization:ID)` or `@[Name](urn:li:person:ID)`. A mention is indivisible — `selected_text` must either contain the entire mention substring or stay outside it. **Required permission:** WRITE access to this social set.
POST /v2/social-sets/{social_set_id}/drafts/{draft_id}/comment-threads - Write
Add a comment to an existing comment thread
Append a comment to an existing comment thread. Returns the full updated thread. **Required permission:** WRITE access to this social set.
POST /v2/social-sets/{social_set_id}/drafts/{draft_id}/comment-threads/{comment_thread_id}/comments - Write
Update a comment's text
Update the plain-text body of a single comment. Returns the full updated thread. **Required permission:** Authorship of the comment.
PATCH /v2/social-sets/{social_set_id}/drafts/{draft_id}/comment-threads/{comment_thread_id}/comments/{comment_id} - Destructive
Resolve a comment thread
Resolves the comment thread and removes the corresponding comment markers from the text. **Required permission:** Either authorship of the comment thread or WRITE access on the social set.
POST /v2/social-sets/{social_set_id}/drafts/{draft_id}/comment-threads/{comment_thread_id}/resolve - Destructive
Delete a comment
Deletes a comment from a comment thread. If `comment_id` identifies the *root* (oldest) comment, the entire thread is deleted and the corresponding comment markers are removed from the text. **Required permission:** Authorship of the comment or WRITE access on the social set.
DELETE /v2/social-sets/{social_set_id}/drafts/{draft_id}/comment-threads/{comment_thread_id}/comments/{comment_id} - Destructive
Delete a comment thread
Deletes the comment thread along with all its comments and removes the corresponding comment markers from the text. **Required permission:** Authorship of the comment thread or WRITE access on the social set.
DELETE /v2/social-sets/{social_set_id}/drafts/{draft_id}/comment-threads/{comment_thread_id}
No operations match.
See How connections work for access and permissions, or browse all integrations.
Reference date: October 29, 2026. Typefully API docs.