canonical: https://jentic.com/apis/windows.net/batchservice

# Windows BatchService

A client for issuing REST requests to the Azure Batch service. The API exposes 70 endpoints.

## For AI agents

Programmatically lists all of the applications available in the specified account., gets information about the specified application.. Covers 70 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Lists all of the applications available in the specified account.
- Gets information about the specified application.
- Adds a certificate to the specified account.
- Certificate_Get
- Deletes a certificate from the specified account.
- Cancels a failed deletion of a certificate from the specified account.

## Use cases

### Developer Tools Operations

Use the BatchService to perform developer tools operations programmatically. The API provides 70 endpoints covering core functionality including lists all of the applications available in the specified account., gets information about the specified application., adds a certificate to the specified account..

Example prompt: Call GET /applications to lists all of the applications available in the specified account.

### Automated Applications Management

Automate applications operations by combining multiple BatchService endpoints. Agents can gets information about the specified application. and then adds a certificate to the specified account. in a single workflow.

Example prompt: Call GET `/applications/{applicationId}` to gets information about the specified application., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call BatchService endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'lists all of the applications available in the specified account.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/applications` | Lists all of the applications available in the specified account. |
| GET | `/applications/{applicationId}` | Gets information about the specified application. |
| POST | `/certificates` | Adds a certificate to the specified account. |
| GET | `/certificates` | Lists all of the certificates that have been added to the specified account. |
| GET | `/certificates(thumbprintAlgorithm={thumbprintAlgorithm},thumbprint={thumbprint})` | Certificate_Get |
| DELETE | `/certificates(thumbprintAlgorithm={thumbprintAlgorithm},thumbprint={thumbprint})` | Deletes a certificate from the specified account. |
| POST | `/certificates(thumbprintAlgorithm={thumbprintAlgorithm},thumbprint={thumbprint})/canceldelete` | Cancels a failed deletion of a certificate from the specified account. |
| POST | `/jobs` | Adds a job to the specified account. |

## Key resources

- **Applications** — Operations for applications
- **Certificates** — Operations for certificates
- **Certificates(Thumbprintalgorithm={Thumbprintalgorithm},Thumbprint={Thumbprint})** — Operations for certificates(thumbprintAlgorithm={thumbprintAlgorithm},thumbprint={thumbprint})
- **Jobs** — Operations for jobs
- **Jobschedules** — Operations for jobschedules

## Why Jentic

- **Setup:** Wiring the Azure Batch BatchService by hand means targeting batch.core.windows.net, handling its per-request auth, and composing job, certificate, and application calls yourself. Through Jentic you install once, import the BatchService from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** BatchService puts the resource id in the URL path (`/applications/{applicationId}`), so a rule can pin your agent to reading one application. You choose the operations it may call, so destructive ones like certificate deletion or job creation are not included unless you add them.
- **Credential handling:** Your Batch credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list applications in a Batch account' or 'submit a job', and Jentic returns the matching BatchService operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the BatchService use?

The BatchService uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I lists all of the applications available in the specified account. with the BatchService?

Yes. Use the GET /applications endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the BatchService?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I lists all of the applications available in the specified account. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'lists all of the applications available in the specified account.'. Jentic returns the matching BatchService operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the BatchService have?

The BatchService exposes 70 endpoints covering applications, certificates, certificates(thumbprintalgorithm={thumbprintalgorithm},thumbprint={thumbprint}) operations.

### Can I limit what my agent is allowed to do with the Azure Batch API?

Yes. Because you run Jentic One yourself, your own rules decide which Azure Batch operations and credentials the agent can use, so you can grant read-only calls like GET /applications or GET `/applications/{applicationId}` while withholding everything else. Since Batch puts the resource id in the URL path, you can pin the agent to a single application. Destructive operations such as deleting a certificate or adding a job are not available to the agent unless you explicitly include them.