Skip to main content
Version: 2019-05-29 (Current)

Bulk pause schedules

Pause one or multiple active charge schedules in a single request. Paused schedules will not execute any occurrences until they are resumed. This is useful for temporarily stopping recurring charges during customer disputes, account holds, or seasonal pauses.

Request Parametersโ€‹

Required - 1 fieldRequired Parameters
โ–ผ
`schedule_ids`ARRAY(required)
Array of schedule IDs to pause. Each ID must start with schd_. Maximum 100 IDs per request.
Example:"[\"schd_test_5xuy4w91xqz7d1w9u0t\", \"schd_test_5xuy4w91xqz7d1w9u0s\"]"
Constraints:Maximum 100 IDs per request, All schedules must be in "active" status

Responsesโ€‹

200

Schedules paused

Returns a summary of the bulk pause operation with details for each schedule.

Response includes:
  • object - Always "bulk_operation"
  • operation - "pause"
  • total_count - Total number of schedule IDs provided
  • successful_count - Number of schedules successfully paused
  • failed_count - Number of schedules that failed to pause
  • results - Array of result objects for each schedule
Each result object includes:
  • schedule_id - The schedule ID
  • status - "success" or "failed"
  • schedule - Updated schedule object (if successful)
  • error_code - Error code (if failed)
  • error_message - Error description (if failed)

400

Bad request

Request validation failed. Check the error message for details.

Common causes:
  • Missing schedule_ids parameter
  • schedule_ids is not an array
  • Empty schedule_ids array
  • More than 100 schedule IDs provided
  • Invalid schedule ID format

401

Unauthorized

Authentication failed. Invalid or missing API key.

Common causes:
  • Missing Authorization header
  • Invalid secret key
  • Using public key instead of secret key
  • Incorrect HTTP Basic Auth format

404

Not found

Endpoint not found or feature not enabled.

Common causes:
  • Bulk operations feature not enabled for account
  • Incorrect API endpoint URL

5xx

Server error

Server-side error occurred. These are rare but should be handled gracefully.

How to handle:

Code samplesโ€‹

# Pause multiple schedules
curl https://api.omise.co/schedules/bulk_pause \
-X PATCH \
-u skey_test_5xuy4w91xqz7d1w9u0t: \
-H "Content-Type: application/json" \
-d '{
"schedule_ids": [
"schd_test_5xuy4w91xqz7d1w9u0t",
"schd_test_5xuy4w91xqz7d1w9u0s",
"schd_test_5xuy4w91xqz7d1w9u0r"
]
}'

Error and result codesโ€‹

Common Error Codesโ€‹

CodeDescriptionResolution
authentication_failureInvalid API keyVerify your secret key is correct
invalid_schedule_idsInvalid or missing schedule_idsProvide valid array of schedule IDs
too_many_idsMore than 100 IDs providedSplit into multiple requests

Per-Schedule Error Codesโ€‹

CodeDescriptionResolution
schedule_not_foundSchedule ID does not existVerify schedule ID is correct
schedule_not_activeSchedule is not in active statusOnly active schedules can be paused
schedule_already_pausedSchedule is already pausedNo action needed
schedule_deletedSchedule has been deletedCannot pause deleted schedules

Schedule Status After Pauseโ€‹

FieldValue
statussuspended
activefalse

๐Ÿ”‘API Credentials

Try it outโ€‹

Required - 1 fields
โ–ผ
Your IP: ...Loading...