> ## Documentation Index > Fetch the complete documentation index at: https://docs.shoply.gg/llms.txt > Use this file to discover all available pages before exploring further. # Create a blog post > Starts a post as a draft with a title and nothing else. Write it and publish it with "Update a blog post". Needs the `blog.write` permission (Change Blog). ## OpenAPI ````yaml /api-reference/openapi.json post /stores/{storeId}/blog/posts openapi: 3.1.0 info: title: Shoply API version: '1' description: >- Everything a store's own server can do with a secret API key: its catalogue, orders, customers, marketing, finance and the rest of what the dashboard does. And the Customer API, which a buyer's own device asks with a token of theirs. servers: - url: https://api.shoply.gg/v1 security: - apiKey: [] tags: - name: API key - name: Store - name: Domain - name: Payment methods - name: Analytics - name: Storefronts - name: Storefront code - name: Payment Routing - name: Custom payment methods - name: Products - name: Product pictures - name: Stock - name: Categories - name: Upsells - name: Subscriptions - name: Orders - name: Invoices - name: Reviews - name: Coupons - name: Coupon categories - name: Coupon pop-up - name: Sales - name: Blog - name: Search settings - name: Redirects - name: Sitemap - name: Cart Recovery - name: Email Marketing - name: Email Templates - name: Customers - name: Affiliates - name: Support Tickets - name: Blacklist - name: Fraud protection - name: Disputes - name: Finance - name: Tax - name: Expenses - name: Expense setup - name: API requests - name: Webhook endpoints - name: Webhook deliveries - name: Customer API paths: /stores/{storeId}/blog/posts: post: tags: - Blog summary: Create a blog post description: >- Starts a post as a draft with a title and nothing else. Write it and publish it with "Update a blog post". Needs the `blog.write` permission (Change Blog). operationId: blogPosts.create parameters: - name: storeId in: path required: true description: >- The store's ID. A key reaches the store it was made in: `GET /key` answers which. schema: type: string - $ref: '#/components/parameters/IdempotencyKey' requestBody: required: true content: application/json: schema: type: object properties: categoryId: type: string description: The blog category it goes in. title: type: string description: Its title. example: How to get started required: - categoryId responses: '201': description: It worked. content: application/json: schema: type: object properties: success: type: boolean message: nullable: true code: nullable: true data: type: object properties: id: type: string categoryId: type: string title: type: string slug: type: string path: type: string status: type: string coverUrl: nullable: true views: type: integer publishedAt: nullable: true updatedAt: type: string body: type: string coverAlt: type: string seoTitle: type: string seoDescription: type: string url: type: string search: type: object properties: title: type: string description: type: string html: type: string checks: type: array items: type: object properties: ok: type: boolean text: type: string example: success: true message: null code: null data: id: 57d066e1-e807-42dc-8d81-b0ff59fa7eb3 categoryId: c3b25928-c119-4d41-8df1-0525a3a69be5 title: Activating Northwind Pro slug: activating-northwind-pro path: /blog/guides/activating-northwind-pro/ status: draft coverUrl: null views: 0 publishedAt: null updatedAt: '2026-10-22 16:20:18.846' body: '' coverAlt: '' seoTitle: '' seoDescription: '' url: >- https://northwind.myshoply.gg/blog/guides/activating-northwind-pro/ search: title: Activating Northwind Pro - Northwind Keys description: '' html: '' checks: - ok: true text: 'The search title fits: 41 of 60 characters' - ok: false text: >- No description. Search engines will use the first lines '401': $ref: '#/components/responses/NoKey' '403': $ref: '#/components/responses/NotAllowed' '404': $ref: '#/components/responses/NotFound' '422': $ref: '#/components/responses/Refused' '429': $ref: '#/components/responses/TooMany' x-codeSamples: - lang: javascript label: Node.js source: | import Shoply from "@shoplygg/node"; const shoply = new Shoply({ apiKey: process.env.SHOPLY_API_KEY }); const result = await shoply.blogPosts.create({ categoryId: "...", }); - lang: php label: PHP source: | getenv('SHOPLY_API_KEY')]); $result = $shoply->blogPosts->create([ 'categoryId' => '...', ]); - lang: python label: Python source: | import shoply client = shoply.Client() # reads SHOPLY_API_KEY result = client.blogPosts.create(categoryId="...") components: parameters: IdempotencyKey: name: Idempotency-Key in: header required: false description: >- A word of your own for this one change, up to 180 letters, digits, dots, dashes, underscores and colons. Sent again with the same key, the request is not carried out twice: the first answer comes back, with `Idempotent-Replay: true`. schema: type: string responses: NoKey: description: >- No API key was sent, or the one sent is not a live key: `api_key_required`, `invalid_api_key`. content: application/json: schema: $ref: '#/components/schemas/Refusal' NotAllowed: description: >- The key is real and may not do this: `missing_scope` (with `requiredScope`), `ip_not_allowed`, `account_unavailable`, or `dashboard_only` for something only a person in the dashboard may do. content: application/json: schema: $ref: '#/components/schemas/Refusal' NotFound: description: >- There is no such thing in this store: `not_found`. A store that is not the key's own is answered the same way. content: application/json: schema: $ref: '#/components/schemas/Refusal' Refused: description: >- The request was understood and not carried out. `validation_failed` says what is wrong with each field under `errors`; other codes are the route's own. content: application/json: schema: $ref: '#/components/schemas/Refusal' TooMany: description: >- The key has used up its budget for now: `rate_limited`. `Retry-After` says how many seconds to wait. content: application/json: schema: $ref: '#/components/schemas/Refusal' schemas: Refusal: type: object properties: success: type: boolean example: false message: type: string description: What is wrong, in words for a person. code: type: string description: What is wrong, as a word that does not change. data: nullable: true errors: type: object description: >- For `validation_failed`: what is wrong with each field, by the field's name. additionalProperties: type: string required: - success - message - code securitySchemes: apiKey: type: http scheme: bearer description: >- A secret API key, made under Developers in the dashboard: `Authorization: Bearer shoply_sk_...` ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.