Skip to main content
Have a question that isn’t answered here? Reach out to us at support@shipstar.ai.

​
General

Shipstar is automated product marketing for engineers and agents. It connects to your GitHub repositories, analyzes your commits, and generates polished marketing content — changelogs, blog posts, social media threads, knowledge base articles, release notes emails, and more.
Shipstar generates 9 types of content:
TypeFormat
Product UpdateMarkdown
Feature BlogMarkdown
Blog PostMarkdown
LinkedIn PostText
Twitter ThreadText
Feature PageJSON
KB ArticlesJSON
Public ChangelogJSON
Release Notes EmailJSON
Shipstar uses Claude to analyze your commits. The AI is prompted to focus on user-facing changes and filter out internal noise like dependency bumps, CI/CD changes, refactors, and code cleanup. The output reads as if written by your team — it never mentions AI or tools.
Yes. All generated content can be reviewed and edited in the dashboard or via the API before publishing. Use the PATCH /sources/content/{content_id} endpoint to update content programmatically.

​
GitHub Integration

Currently, Shipstar supports GitHub. Connect via OAuth and select which repositories to track.
Yes. When you connect your GitHub account, you authorize Shipstar to access your repositories. Both public and private repos can be tracked.
Yes. You can track as many repositories as you like. When generating content, Shipstar aggregates commits from all active tracked repos into a single piece of content.
By default, Shipstar analyzes the last 7 days of commits. You can specify a custom date range with the start_date and end_date parameters when triggering content generation.

​
Publishing & Distribution

Use the publish endpoint: POST /content/{content_id}/publish. This generates a unique public URL where the content is accessible without authentication. You can also unpublish at any time.
Yes. Published changelogs and blog posts automatically include RSS feeds at /feed appended to the public URL. There’s also a combined feed for all blog posts at /api/v1/blogs/feed.
Yes. Shipstar can push any content type directly to a connected Slack channel.
Yes. Shipstar integrates with Intercom to sync generated knowledge base articles directly to your help center.

​
Scheduling

Yes. Shipstar supports calendar events that trigger content generation on a schedule. Set up recurring events — for example, a weekly changelog every Friday or a monthly blog post on the 1st.
Events follow the RFC 5545 RRULE standard, so you can configure daily, weekly, monthly, or custom recurrence patterns.

​
API & Authentication

  1. Sign up at app.shipstar.ai
  2. Navigate to the Dashboard
  3. Click API Keys in the sidebar
  4. Create a new API key and copy it
See the Quickstart guide for detailed instructions.
The API uses Bearer token authentication. Include your API key in the Authorization header:
Authorization: Bearer YOUR_API_KEY
Public content endpoints (changelogs, blogs, KB articles accessed by slug) don’t require authentication.
No. Content generation runs asynchronously. When you trigger a generation request, you receive a content_id and status: "pending". Poll the content endpoint to check when it’s complete. The status transitions from pending → processing → completed (or failed).
Usage is based on your subscription plan. Check your current usage and plan details in the dashboard under Subscription.

​
Privacy & Data

Shipstar accesses commit metadata (message, author, date, SHA) from your tracked GitHub repositories. It does not access file contents, pull request discussions, or issues — only commit messages.
Generated content and your repository data are only accessible via authenticated API requests using your API key. Published content is accessible at its public URL by design.
Yes. You can disconnect your GitHub account at any time from the dashboard or via the API. This removes all tracked repositories and revokes access.

​
Still have questions?

Contact Support

Reach out to the Shipstar team and we’ll get back to you