canonical: https://jentic.com/apis/azure.com/datalakeanalyticscatalogmanagementclient

# Microsoft Azure DataLakeAnalyticsCatalogManagementClient

Jentic publishes the only available OpenAPI specification for DataLakeAnalyticsCatalogManagementClient, keeping it validated and agent-ready. The API exposes the U-SQL catalog of an Azure Data Lake Analytics account so callers can browse and inspect databases, schemas, tables, views, table-valued functions, stored procedures, assemblies, credentials, and ACLs. It is read-oriented over the catalog plus credential mutation endpoints, and is the path agents use to discover the shape of analytics data before submitting jobs. All 45 operations live under the /catalog/usql/* path tree.

## For AI agents

Browse and inspect the U-SQL catalog of an Azure Data Lake Analytics account - list databases, tables, views, schemas, assemblies, and ACLs, and manage credential entries.

## Scope

Does not submit U-SQL jobs, manage Data Lake Analytics accounts, or read raw lake files - use for U-SQL catalog metadata and credential management only.

## Capabilities

- List U-SQL databases, schemas, tables, and views in a Data Lake Analytics catalog
- Inspect table schemas, table statistics, partitions, types, and table-valued functions
- Retrieve assemblies, stored procedures, and external data sources for a database
- Read and modify catalog ACLs at account and database scope
- Create, update, retrieve, and delete catalog credential entries used by U-SQL jobs
- List and inspect packages and column-level statistics within a U-SQL database

## Use cases

### Pre-job catalog inspection

Before submitting a U-SQL job to Azure Data Lake Analytics, an analyst or agent inspects the target catalog to confirm tables, schemas, and types match the job script. The catalog API returns database, schema, table, and column metadata so the job author can validate references against the live catalog instead of a stale data dictionary.

Example prompt: List all tables in the database 'sales' on the Data Lake Analytics account and return the column list for the table 'orders'

### Catalog credential management for U-SQL jobs

U-SQL scripts that pull from external systems (Azure SQL Database, blob, etc.) need credential entries registered in the catalog. The credentials endpoints let an automation flow create, rotate, and delete those entries against a specific U-SQL database without manual portal steps.

Example prompt: Create a catalog credential named 'sql-prod-reader' on database 'sales' with the supplied user identity and password, then verify it appears in the credential list

### Catalog ACL audit

Compliance checks routinely verify which principals have access to U-SQL databases. The ACL list endpoints return the full set of ACL entries at account or database scope so an audit script can reconcile actual permissions against an expected access matrix.

Example prompt: Retrieve the ACL list for database 'finance' and flag any principal that is not in the approved auditor allowlist

### Agent-driven analytics catalog discovery

An AI agent asked to answer a business question against Data Lake Analytics first needs to know what data exists. Through Jentic, the agent searches for catalog discovery operations, lists databases and tables, then composes a U-SQL query against the resolved schema. The catalog API is the agent's source of truth for what U-SQL objects exist.

Example prompt: Discover all tables in databases on the Data Lake Analytics account that contain a column named 'customer_id' and return their fully qualified names

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /catalog/usql/databases | List U-SQL databases in the catalog |
| GET | /catalog/usql/databases/{databaseName} | Get a specific U-SQL database |
| GET | /catalog/usql/databases/{databaseName}/schemas/{schemaName}/tables | List tables in a schema |
| GET | /catalog/usql/databases/{databaseName}/credentials | List catalog credentials in a database |
| GET | /catalog/usql/databases/{databaseName}/acl | List ACL entries for a database |
| GET | /catalog/usql/databases/{databaseName}/assemblies | List assemblies registered in a database |
| GET | /catalog/usql/databases/{databaseName}/procedures | List stored procedures in a database |

## Key resources

- **Databases** — List and inspect U-SQL databases in the catalog
- **Tables and Schemas** — Browse tables, schemas, columns, partitions, statistics, and types within a database
- **Views and TVFs** — Retrieve U-SQL views and table-valued functions defined in a database
- **Assemblies and Procedures** — List assemblies, stored procedures, and packages registered in a U-SQL database
- **Credentials** — Create, read, update, and delete catalog credential entries used by U-SQL jobs
- **ACLs** — Read and modify access control entries at account and database scope

## Why Jentic

- **Setup:** Wiring the Azure Data Lake Analytics catalog by hand means resolving the per-account host from the {accountName}.{adlaCatalogDnsSuffix} template, obtaining an Azure AD bearer token for the Data Lake Analytics resource, and threading it onto every catalog call yourself. Through Jentic you install once, import Data Lake Analytics Catalog Management from the API Directory, store the Azure credential once, and your agent calls it.
- **Permission scoping:** The catalog puts the database and schema names in the URL path (/catalog/usql/databases/{databaseName}/schemas/{schemaName}/...), so a rule can pin your agent to one database's metadata. You choose the operations it may call, so mutating ones like the credential create-or-delete endpoints are not included unless you add them, leaving the agent on read-only listing operations.
- **Credential handling:** Your Azure credential is stored once, encrypted, by your own Jentic One instance and injected as a scoped bearer token at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list U-SQL databases' or 'get a table schema in Data Lake Analytics', and Jentic returns the matching catalog operation with its input schema so the agent inspects the catalog without scraping the reference docs.

## Related APIs

- **DataLakeStoreAccountManagementClient** — Manages the underlying Data Lake Store account that backs an Analytics account
- **DataLakeStoreFileSystemManagementClient** — Reads and writes raw files in Data Lake Store
- **DataShareManagementClient** — Shares datasets across Azure subscriptions instead of querying a U-SQL catalog

## FAQ

### Why is there no official OpenAPI spec for DataLakeAnalyticsCatalogManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DataLakeAnalyticsCatalogManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Data Lake Analytics Catalog API use?

The catalog client itself reaches an account-specific endpoint (typically https://{accountName}.azuredatalakeanalytics.net) and is gated by Azure Active Directory bearer tokens issued for the Data Lake Analytics resource. Through Jentic, the AAD credential is held in the encrypted vault and a scoped token is supplied at execute time so the bearer token never enters the agent's prompt context.

### Can I list all tables in a U-SQL database with this API?

Yes. Call GET /catalog/usql/databases/{databaseName}/schemas/{schemaName}/tables to enumerate tables under a specific schema, or use the per-database listing endpoints to walk schemas first. Combined with the table-detail endpoint you can retrieve column lists, partitioning, and statistics for each table.

### What are the rate limits for the Data Lake Analytics Catalog API?

Azure Data Lake Analytics applies subscription-level throttling rather than per-endpoint rate caps; sustained polling against catalog list endpoints can return HTTP 429 responses with a Retry-After hint. Treat the catalog as a metadata store and cache results for the duration of a job rather than calling list operations on every step.

### How do I rotate a U-SQL catalog credential through Jentic?

Search Jentic for 'rotate u-sql catalog credential', load the schema for PUT /catalog/usql/databases/{databaseName}/credentials/{credentialName}, then execute with the new credential payload. The pip install jentic Python SDK uses the async search, load, execute pattern and reads JENTIC_AGENT_API_KEY from your environment.

### Is the Data Lake Analytics Catalog API free?

There is no separate charge for catalog metadata calls beyond standard Azure Data Lake Analytics pricing - you pay for the underlying account, storage, and any U-SQL job hours consumed. Catalog reads do not bill per-request.

### Can I limit what my agent is allowed to do with the Azure Data Lake Analytics Catalog API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which catalog operations and credentials your agent may use. Since the database and schema names sit in the URL path, such as /catalog/usql/databases/{databaseName}/schemas/{schemaName}, you can pin the agent to a single database's metadata. You also choose which operations it can call, so you can leave it on read-only listing endpoints like GET /catalog/usql/databases and exclude the credential create and delete operations unless you deliberately add them.