Windows GraphRbacManagementClient
Browse all Windows APIsHR recruitingRecruiting Atsoauth256 EndpointsREST
For Agents
Programmatically applications_create, applications_list. Covers 56 operations with oauth2 authentication.
Use for: I need to applications_create, I want to applications_list, Search for applications_get, Find all applications_patch
Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.
The Graph RBAC Management Client. The API exposes 56 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the GraphRbacManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GraphRbacManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fwindows.net%2Fgraphrbacmanagementclient" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fwindows.net%2Fgraphrbacmanagementclient" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with GraphRbacManagementClient API.
Applications_Create
Applications_List
Applications_Get
Applications_Patch
Applications_Delete
Applications_AddOwner
Applications_RemoveOwner
Use Cases
Patterns agents use GraphRbacManagementClient API for, with concrete tasks.
★ HR and Recruiting Operations
Use the GraphRbacManagementClient to perform hr recruiting operations programmatically. The API provides 56 endpoints covering core functionality including applications_create, applications_list, applications_get.
Call POST /{tenantID}/applications to applications_create
Automated Applications Management
Automate applications operations by combining multiple GraphRbacManagementClient endpoints. Agents can applications_list and then applications_get in a single workflow.
Call GET /{tenantID}/applications to applications_list, then verify the result
AI Agent Integration via Jentic
AI agents discover and call GraphRbacManagementClient 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 oauth2 tokens manually.
Search Jentic for 'applications_create', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
56 endpoints — the graph rbac management client.
METHOD
PATH
DESCRIPTION
POST
/{tenantID}/applications
Applications_Create
GET
/{tenantID}/applications
Applications_List
GET
/{tenantID}/applications/{applicationObjectId}
Applications_Get
PATCH
/{tenantID}/applications/{applicationObjectId}
Applications_Patch
DELETE
/{tenantID}/applications/{applicationObjectId}
Applications_Delete
POST
/{tenantID}/applications/{applicationObjectId}/$links/owners
Applications_AddOwner
DELETE
/{tenantID}/applications/{applicationObjectId}/$links/owners/{ownerObjectId}
Applications_RemoveOwner
GET
/{tenantID}/applications/{applicationObjectId}/keyCredentials
Applications_ListKeyCredentials
POST
/{tenantID}/applications
Applications_Create
GET
/{tenantID}/applications
Applications_List
GET
/{tenantID}/applications/{applicationObjectId}
Applications_Get
PATCH
/{tenantID}/applications/{applicationObjectId}
Applications_Patch
DELETE
/{tenantID}/applications/{applicationObjectId}
Applications_Delete
POST
/{tenantID}/applications/{applicationObjectId}/$links/owners
Applications_AddOwner
DELETE
/{tenantID}/applications/{applicationObjectId}/$links/owners/{ownerObjectId}
Applications_RemoveOwner
GET
/{tenantID}/applications/{applicationObjectId}/keyCredentials
Applications_ListKeyCredentials
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the GraphRbacManagementClient by hand means running the Azure Active Directory OAuth2 flow against login.microsoftonline.com, targeting graph.windows.net, and threading the tenant id through every path yourself. Through Jentic you install once, import the GraphRbacManagementClient from the API Directory, store the OAuth client once, and your agent calls it.
Permission scoping
GraphRbac puts the tenant and application ids in the URL path (/{tenantID}/applications/{applicationObjectId}), so a rule can pin your agent to reading applications within one tenant. You choose the operations it may call, so destructive ones like application deletion or removing an owner are not included unless you add them.
Credential isolation
Your Azure AD OAuth client 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.
Intent-based discovery
Agents search Jentic by intent such as 'list applications in a tenant' or 'read an application's key credentials', and Jentic returns the matching GraphRbac operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using GraphRbacManagementClient API through Jentic.
What authentication does the GraphRbacManagementClient use?
The GraphRbacManagementClient uses OAuth 2.0 for authorization. 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 applications_create with the GraphRbacManagementClient?
Yes. Use the POST /{tenantID}/applications endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the GraphRbacManagementClient?
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 applications_create through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'applications_create'. Jentic returns the matching GraphRbacManagementClient operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the GraphRbacManagementClient have?
The GraphRbacManagementClient exposes 56 endpoints covering applications, deletedapplications, domains operations.
Can I limit what my agent is allowed to do with the GraphRbacManagementClient API?
Yes. Jentic One is self-hosted, so your own rules decide which GraphRbac operations and OAuth credentials the agent may use. Because the tenant and application ids sit in the URL path (/{tenantID}/applications/{applicationObjectId}), you can pin the agent to reading applications within a single tenant, and you choose exactly which operations it may call. Destructive calls such as application deletion or removing an owner stay out of reach unless you explicitly grant them.
GET STARTED