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

Bulk resume schedules

Resume one or multiple paused charge schedules in a single request. Resumed schedules will return to active status and begin executing on their next scheduled occurrence. This is useful for reactivating schedules after temporary holds or seasonal pauses.

Request Parametersโ€‹

Required - 1 fieldRequired Parameters
โ–ผ
`schedule_ids`ARRAY(required)
Array of schedule IDs to resume. 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 "suspended" status

Responsesโ€‹

200

Schedules resumed

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

Response includes:
  • object - Always "bulk_operation"
  • operation - "resume"
  • total_count - Total number of schedule IDs provided
  • successful_count - Number of schedules successfully resumed
  • failed_count - Number of schedules that failed to resume
  • 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โ€‹

# Resume multiple paused schedules
curl https://api.omise.co/schedules/bulk_resume \
-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_suspendedSchedule is not in suspended statusOnly paused schedules can be resumed
schedule_already_activeSchedule is already activeNo action needed
schedule_deletedSchedule has been deletedCannot resume deleted schedules
schedule_expiredSchedule has passed its end dateCreate a new schedule

Schedule Status After Resumeโ€‹

FieldValue
statusactive
activetrue

๐Ÿ”‘API Credentials

Try it outโ€‹

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