Myown APImyown.website ↗
Access MyOwnWebsite.com blog posts via API. List paginated post summaries or fetch full article content by slug for salon, spa, and pet care topics.
What is the Myown API?
The MyOwnWebsite.com Blog API provides 2 endpoints for accessing business management articles aimed at service industries such as salons, spas, and pet care facilities. Use list_blog_posts to retrieve paginated summaries including title, slug, description, image URL, published date, and author, or call get_blog_post with a slug to fetch the complete article text alongside metadata like featured image and meta description.
curl -X GET 'https://api.parse.bot/scraper/1283a7e0-0027-4638-9009-6e31e7be599f/list_blog_posts?page=1&items_per_page=5' \ -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 myown-website-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.
"""Walkthrough: MyOwnWebsite Blog API — browse posts and read full articles."""
from parse_apis.myownwebsite_blog_api import MyOwnWebsite, PostNotFound
client = MyOwnWebsite()
# List recent blog posts (most recent first), capped at 5 items total.
for summary in client.postsummaries.list(limit=5):
print(summary.title, "|", summary.published_date)
# Drill into the first accessible post for its full content.
first = client.postsummaries.list(limit=1).first()
if first:
detail = first.details()
print(detail.title, detail.published_date)
print(detail.content[:200])
# Direct lookup by slug via the posts collection.
try:
post = client.posts.get(slug="blog/how-to-open-salon")
print(post.title, post.author, post.description[:80])
except PostNotFound as exc:
print(f"Post not found: {exc.slug}")
print("exercised: postsummaries.list / PostSummary.details / posts.get / PostNotFound")
List blog posts with pagination. Returns post summaries including title, slug, image, description, published date, and author. Posts are ordered most-recent-first. Each page contains up to items_per_page results; use the has_next_page flag or the SDK's automatic pagination to walk the full archive.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (starts at 1). |
| items_per_page | integer | Number of posts per page, between 1 and 20. |
{
"type": "object",
"fields": {
"page": "integer - current page number",
"posts": "array of blog post summaries with title, slug, image_url, description, published_date, and author",
"has_next_page": "boolean - whether more posts exist after this page",
"items_per_page": "integer - number of posts per page",
"has_previous_page": "boolean - whether posts exist before this page"
}
}About the Myown API
Endpoints and Data Coverage
The API exposes two endpoints covering the MyOwnWebsite.com blog. list_blog_posts returns an array of post summaries ordered by most recent first, with each entry containing a title, slug, image_url, description, published_date, and author. Pagination is controlled via the page parameter (starting at 1) and items_per_page (1–20). The response includes has_next_page and has_previous_page booleans so you can walk the full archive programmatically.
Full Article Retrieval
get_blog_post accepts a slug string — for example blog/client-intake-form-automation or best-salon-software — and returns the complete article. The response includes content as a string formatted with markdown-style headings, plus featured_image, description (the meta description), author, and published_date. Both author and featured_image can be null if not present on the source post.
Scope and Content
All content originates from the MyOwnWebsite.com blog, which focuses on operational tips for service businesses: appointment scheduling, client management, software comparisons, and marketing guidance for salons, spas, barbershops, and pet care providers. Posts are ordered chronologically descending, so page 1 always reflects the most recently published content.
The Myown API is a managed, monitored endpoint for myown.website — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when myown.website 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 myown.website 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?+
- Aggregate salon and spa software guides into an industry knowledge base using
contentfromget_blog_post - Build an RSS-style feed of new service-business articles by polling
list_blog_postsand checkingpublished_date - Index post summaries including
descriptionandtitlefor a domain-specific search engine covering pet care and spa management topics - Extract
featured_imageandtitlefields from post summaries to populate a content preview widget - Pull full article
contentfor LLM fine-tuning or RAG pipelines focused on service-business operations - Monitor the MyOwnWebsite.com blog for new posts by paginating with
has_next_pageand tracking slugs - Compile author-attributed article archives using the
authorfield returned by both endpoints
| 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 MyOwnWebsite.com have an official developer API?+
What does `list_blog_posts` return compared to `get_blog_post`?+
list_blog_posts returns summary-level fields — title, slug, image_url, description, published_date, and author — for multiple posts per page. get_blog_post returns those same metadata fields for a single post plus the full content string formatted with markdown-style headings. The content field is only available from get_blog_post.Can I filter posts by category, tag, or author?+
page and items_per_page parameters; there are no filter parameters for category, tag, or author. You can fork this API on Parse and revise it to add a filtering endpoint if those dimensions are available on the source.Are non-blog pages like product features or pricing pages accessible?+
list_blog_posts and get_blog_post. You can fork this API on Parse and revise it to add an endpoint targeting other page types on the site.How current is the post data, and how is pagination ordered?+
list_blog_posts reflects the latest published content. The published_date field on each post indicates when it was originally published. Freshness depends on how frequently the API is called; there is no built-in webhook or delta mechanism.