microCMS
Documentation
  • Pricing
  • Blog
  • FAQ
  • Contact
  • Sign In
  • Get started for free
Navigation
Tutorial
Next.js
  • Integration with Next.js
  • Getting Started with App Router
  • Tutorial (App Router)
  • Getting Started with Pages Router
  • Tutorial (Pages Router)
Astro
  • Getting Started
  • Integration with Astro
  • Tutorial
Nuxt
  • Integration with Nuxt
  • Getting Started
  • Tutorial
Gatsby
  • Integration with Gatsby
  • Getting Started
  • Tutorial
JavaScript
  • Integration with JavaScript
  • Getting Started (Browser)
  • Getting Started (Server)
PHP
  • Integration with PHP
  • Getting Started
Ruby
  • Integration with Ruby
  • Getting Started
Go
  • Integration with Go
  • Getting Started with microCMS
Manual
  • Introduction
Account & Login
  • Account Registration
  • Login
  • Email Address Authentication
Services
  • Creating a Service
  • Service Configuration
  • Template
  • Service Deletion
Payment
  • Change of Pricing Plan
  • Registering and Changing Payment Methods
API
  • Creating and Managing APIs
  • API Settings
  • Export/Import of API Schema
Fields
  • Text Field
  • Text Area
  • Image
  • Multiple Images
  • Date
  • Boolean
  • Selectable Field
  • Content Reference
  • Multiple Content References
  • Number
  • File
  • Extended Field
  • Repetition
  • Custom
Contents
  • CSV Export of Content
  • Content Creation
  • Content Editing
  • Content Management
  • View
  • Content Status
  • Custom Status
  • Setting the Content ID
  • Automatically Assigned Values for Content
  • CSV Import of Content
  • API Preview
  • Examples of Using Query Parameters with API Preview
  • Integration Methods by Rendering Type
  • Screen Preview
  • Setting Up Webhooks for Content
Rich Editor
  • How to Use the Rich Editor
  • Rich Editor WRITE API
  • How to Use the Old Rich Editor
Reviews
  • Review
  • AI Review
Media
  • Media Management
  • Changing Media Filters and Display Order
  • Media Tag Configuration
  • Setting Up Media Webhooks
  • Custom Domain Settings for Media
Permission Management
  • Member Management
  • Roles (Permission Management in the Admin Panel)
Environments
  • Multiple Environments (Development Environment)
  • Merging API Settings Between Environments
Connection
  • Amazon S3 Integration
Logs
  • Audit Log
  • Data Transfer Volume
Security
  • Content Update History
  • IP Restrictions for Management Dashboard
  • IP Restrictions for APIs
Authentication
  • Setting Up Two-Factor Authentication
  • Mandatory Two-Factor Authentication
  • Single Sign-On
Specifications & Limitations
  • Recommended Environment
  • Limitations / Precautions
Content API
  • What is the Content API?
Basic Operations
  • GET /api/v1/{endpoint}
  • GET /api/v1/{endpoint}/{content_id}
  • POST /api/v1/{endpoint}
  • PUT /api/v1/{endpoint}/{content_id}
  • PATCH /api/v1/{endpoint}/{content_id}
  • DELETE /api/v1/{endpoint}/{content_id}
API Keys
  • API Key (API Authentication and Authorization Management)
  • Migration from the Old API (X-API-KEY, etc.)
Responses & Error Handling
  • Response format for each field in the GET API
  • Specifying Query Parameters in the GET API
  • Error Responses of the Content API
Management API (Beta)
  • What is the Management API?
Content Operations
  • PUT /api/v1/contents/{endpoint}/{content_id}/reservation
  • GET /api/v1/contents/{endpoint}
  • GET /api/v1/contents/{endpoint}/{content_id}
  • PATCH /api/v1/contents/{endpoint}/{content_id}/status
  • PATCH /api/v1/contents/{endpoint}/{content_id}/createdBy
Media Operations
  • GET /api/v2/media
  • GET /api/v1/media
  • POST /api/v1/media
  • DELETE /api/v2/media
Member Operations
  • GET /api/v1/members
  • GET /api/v1/members/{member_id}
API Operations
  • POST /api/v1/apis
  • GET /api/v1/apis
  • GET /api/v1/apis/{endpoint}
Service Operations
  • GET /api/v1/service
Responses & Error Handling
  • Management API Error Responses
Image API
  • What is the Image API?
Parameters
  • Image Size
  • Quality
  • Resolution and Screen Size
  • Format
  • Text
  • Border
  • Padding
  • Shape
  • Download
  • Watermark
MCP Server
  • microCMS MCP
  • microCMS Document MCP Server
  • Top
  • Management API (Beta)

PUT /api/v1/contents/{endpoint}/{content_id}/reservation

Last updated: 2026/06/22

This is an API that allows you to schedule the start and end of content publication.
You can also cancel any scheduled reservations that have been set.

Request Headers

X-MICROCMS-API-KEY

This is the authentication key required for requests to the Management API.
Please enable the default permission "Change Content Scheduling" for the Management API and include it in the request headers when sending.

Caution

If the X-MICROCMS-API-KEY is identifiable, it may allow unauthorized manipulation of content by third parties. Please handle it with care. For more details, please refer to "API Key (API Authentication and Permission Management)".

Content-Type

Specify the format of the data to be sent.
Since microCMS only handles data in JSON format, please specify application/json.

Request Body

Please specify the publishTime and stopTime.

// When setting both publish time and stop time
// ※Existing publish start and end settings will be overwritten
{ "publishTime": "2026-01-13T06:31:24.668Z", "stopTime": "2026-01-14T06:31:24.668Z" }

// When setting only the publish time
// ※Existing publish end setting will be removed
{ "publishTime": "2026-01-13T06:31:24.668Z" }

// When setting only the stop time
// ※Existing publish start setting will be removed
{ "stopTime": "2026-01-14T06:31:24.668Z" }

// When removing existing publish start and end schedule settings
{}


Time Format

Specify as an ISO 8601 formatted date-time string.
Acceptable formats include the following:

  • UTC (ending with Z)
    • Example: 2026-01-14T06:31:24.668Z
  • UTC (without Z)
    • Example: 2026-01-14T06:31:24.668
    • If there is no Z, it will be interpreted as UTC (the example time is equivalent to 2026-01-14T06:31:24.668Z)
  • With time zone (offset)
    • Example: 2026-01-14T15:31:24.668+09:00
    • The offset will be interpreted and registered as UTC (the above example will be treated as 2026-01-14T06:31:24.668Z)

Notes

  • null / "" will result in an error.
  • If there are existing publish start/end settings, they will be overwritten.
  • If only one is specified in the request body, the schedule setting for the other will be removed.
  • Sending an empty JSON object ({}) will remove the existing publish start and end schedule settings.

Response

Status Code

If the update is successful, a 200 response will be returned.

Response Body

If the update is successful, a response like the following will be returned.

{ "id": "some_content_id" }


Contents

  • Request Headers
  • X-MICROCMS-API-KEY
  • Content-Type
  • Request Body
  • Time Format
  • Notes
  • Response
  • Status Code
  • Response Body
  • Company
  • Legal Notice
  • Terms of Service
  • Privacy Policy

Copyright © microcms.io All rights reserved.