SoundBoost APIsoundboost.ai ↗
Access SoundBoost blog posts on music production, mastering, and audio engineering, plus current membership pricing plans via 3 structured endpoints.
What is the SoundBoost API?
The SoundBoost API covers 3 endpoints that expose the site's blog content and subscription pricing. The get_blog_posts endpoint returns a filterable list of articles on music production, mastering, and audio engineering, including titles, excerpts, author names, publication dates, and featured image URLs. get_blog_post returns the full HTML content and metadata for a single article by slug, while get_pricing delivers current plan details for Pro and Unlimited tiers.
curl -X GET 'https://api.parse.bot/scraper/82f8895f-a1a3-4150-b35f-4b3665850658/get_blog_posts?category=Tips+%2F+Tricks' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace soundboost-ai-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.soundboost_blog___pricing_api import SoundBoost, PostCategory, PostNotFound
client = SoundBoost()
# List blog posts filtered by category
for summary in client.postsummaries.list(category=PostCategory.TIPS_TRICKS):
print(summary.title, summary.author, summary.date)
# Get full post details from a summary
first_summary = next(iter(client.postsummaries.list(category=PostCategory.NEWS)))
full_post = first_summary.details()
print(full_post.title, full_post.content, full_post.tags)
# Fetch a post directly by slug
post = client.posts.get(slug="track-vs-stem-why-the-difference-still-matters")
print(post.title, post.author, post.category)
# List all pricing plans
for plan in client.plans.list():
print(plan.name, plan.price, plan.original_price, plan.gained_credits)
Retrieve all blog posts from SoundBoost. Optionally filter by category. Returns post metadata including title, excerpt, author, date, and featured image URL. All posts returned in a single page.
| Param | Type | Description |
|---|---|---|
| category | string | Filter posts by category name (case-insensitive). Omitting returns all posts. |
{
"type": "object",
"fields": {
"posts": "array of blog post summaries",
"total": "integer count of returned posts"
},
"sample": {
"data": {
"posts": [
{
"id": 391,
"date": "2025-12-28T17:07:33",
"slug": "track-vs-stem-why-the-difference-still-matters",
"title": "Track vs Stem: Why the Difference Still Matters",
"author": "Ufuk Önen",
"excerpt": "<p>“Can you do stem mastering if I send you the tracks?”</p>",
"category": "Tips / Tricks",
"modified": "2025-12-28T17:17:23",
"featured_image": "https://primary-production-2608.up.railway.app/wp-content/uploads/2025/12/soundbooststemsplitter.jpg"
}
],
"total": 26
},
"status": "success"
}
}About the SoundBoost API
Blog Post Listing
The get_blog_posts endpoint returns an array of post summaries plus a total count. Each entry includes title, excerpt, author, date, and the featured image URL. You can narrow results using the optional category parameter — known categories include Tips / Tricks and News from SoundBoost — and matching is case-insensitive. This endpoint is suited for building article indexes, content feeds, or monitoring when new posts appear.
Single Post Detail
get_blog_post accepts a required slug parameter (for example, track-vs-stem-why-the-difference-still-matters) and returns the full content field as an HTML string alongside title, author, date, modified, category, tags (an array of strings), excerpt, and the integer id. The modified field lets you detect edits after initial publication. Slugs for available posts can be discovered from the listing endpoint.
Pricing Plans
get_pricing takes no inputs and returns a plans array. Each plan object includes the tier name, current price, original (pre-discount) price, and credit allocation. This is useful for surfacing current SoundBoost plan options in comparison tools or tracking price changes over time without manual checks.
The SoundBoost API is a managed, monitored endpoint for soundboost.ai — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when soundboost.ai changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official soundboost.ai API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a music production content feed filtered to the 'Tips / Tricks' category using
get_blog_posts. - Detect edits to existing SoundBoost articles by comparing the
modifiedfield fromget_blog_postover time. - Index SoundBoost article tags and authors to analyze content themes across the blog.
- Track SoundBoost subscription price changes by periodically polling
get_pricingand logging plan prices. - Render full article content on a custom dashboard by fetching HTML from
get_blog_postusing discovered slugs. - Monitor when SoundBoost publishes new posts in the 'News from SoundBoost' category by watching the
totalcount. - Compare SoundBoost Pro and Unlimited plan credit allocations and original vs. current prices for a pricing comparison page.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does SoundBoost have an official developer API?+
What does `get_blog_post` return beyond what the listing endpoint provides?+
get_blog_post adds the full content field (complete HTML of the article body), a tags array, the integer id, and a modified ISO datetime indicating the last edit. The listing endpoint returns only summary fields: title, excerpt, author, date, and featured image URL.Does the API expose individual audio processing jobs, user accounts, or stem-splitting results from SoundBoost?+
Are there pagination controls for `get_blog_posts`?+
total count. You can fork the API on Parse and revise it to add pagination inputs if the volume of posts makes that necessary.Can I retrieve posts by author or by tag using the existing endpoints?+
get_blog_posts accepts only a category filter. Individual post tags are available in the tags array from get_blog_post, so you could fetch posts via the listing endpoint and filter client-side by tag. You can also fork the API on Parse and revise it to add a dedicated tag or author filter parameter.