Skip to content
Cloud infrastructure/devops

windows.net:batch-BatchService

BatchService sandbox and mock API

A client for issuing REST requests to the Azure Batch service. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
73
Collections
-
Event types
-
Start this simulation
example request
curl https://your-windows-batch-batchservice.slurry.io/applications \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2018-08-01.7.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 73.

  • GET/applications
  • GET/applications/{applicationId}
  • GET/certificates
  • POST/certificates
  • GET/certificates(thumbprintAlgorithm={thumbprintAlgorithm},thumbprint={thumbprint})
  • DELETE/certificates(thumbprintAlgorithm={thumbprintAlgorithm},thumbprint={thumbprint})
  • POST/certificates(thumbprintAlgorithm={thumbprintAlgorithm},thumbprint={thumbprint})/canceldelete
  • GET/jobs
  • POST/jobs
  • GET/jobs/{jobId}
  • PUT/jobs/{jobId}
  • PATCH/jobs/{jobId}