Skip to main content
curl -X POST "https://api.a1base.com/v1/cron-jobs/{accountId}/trigger/550e8400-e29b-41d4-a716-446655440000" \
  -H "X-API-Key: your-api-key" \
  -H "X-API-Secret: your-api-secret"

{
  "data": {
    "execution_id": "exe_123456789",
    "status": "success",
    "response_code": 200,
    "response_body": "{\"message\": \"Report generated successfully\", \"report_id\": \"rpt_98765\"}",
    "executed_at": "2024-01-25T15:45:00Z"
  }
}
Manually trigger a cron job execution immediately, regardless of its schedule. This is useful for testing or when you need to run a job outside its normal schedule.

​
Path Parameters

​
accountId
string
required
Your A1Base account ID
​
cron_job_id
string
required
The unique identifier of the cron job to trigger (UUID format)

​
Response

​
data
object
Execution result information
Manual triggers bypass the schedule and execute immediately. The job must be active (is_active: true) to be triggered.
curl -X POST "https://api.a1base.com/v1/cron-jobs/{accountId}/trigger/550e8400-e29b-41d4-a716-446655440000" \
  -H "X-API-Key: your-api-key" \
  -H "X-API-Secret: your-api-secret"

{
  "data": {
    "execution_id": "exe_123456789",
    "status": "success",
    "response_code": 200,
    "response_body": "{\"message\": \"Report generated successfully\", \"report_id\": \"rpt_98765\"}",
    "executed_at": "2024-01-25T15:45:00Z"
  }
}

​
Use Cases

Test your endpoint before enabling scheduled execution:
  1. Create the cron job with is_active: false
  2. Trigger it manually to verify it works
  3. Update to is_active: true when ready
Run scheduled tasks outside their normal schedule:
  • Generate reports on demand
  • Process data immediately
  • Respond to user actions
When a scheduled execution fails:
  1. Check the logs to understand the issue
  2. Fix the problem
  3. Manually trigger to verify the fix
Use manual triggers for initial setup:
  • Load historical data
  • Populate caches
  • Initialize systems

​
Important Notes

  • The cron job must be active (is_active: true) to be triggered
  • Manual triggers count towards your API rate limits
  • Execution follows the same retry logic as scheduled runs
  • Webhook callbacks will be triggered as configured

​
Error Responses

​
404 Not Found
Cron job not found
{
  "detail": "Cron job not found"
}
​
400 Bad Request
Cron job is not active
{
  "detail": "Cron job is not active"
}