Admina API

Name: Admina API API
Brand: Admina API
Availability: InStock

✓ Official Vendor SpecIdentity AuthDirectory Servicesbearer57 EndpointsREST

For Agents

Pull a full picture of an organisation's SaaS users, devices, and licences from Admina, and run joiner-mover-leaver workflows against connected services.

Quickstart

Get started with Admina API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list all users in our SaaS organisation"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Admina API API.

List every user in the organisation along with their connected service accounts and risk signals

Merge duplicate identities across services so a single employee maps to one Admina identity record

Inventory connected SaaS services and the per-service account assignments per employee

Trigger workflow runs that provision or deprovision SaaS access when someone joins or leaves

GET STARTED

Start building with Admina API API

Explore with Jentic

View OpenAPI Spec

Use for: I need to list all SaaS accounts a leaving employee owns, Merge two Admina identities that belong to the same person, Find all admin users across our connected SaaS services, Trigger an offboarding workflow for user u_123

Not supported: Does not handle accounting, payroll, or financial transactions despite the Money Forward name — use for SaaS identity, accounts, and access management on Admina only.

Use Cases

Patterns agents use Admina API API for, with concrete tasks.

★ Automated SaaS Offboarding

When an employee leaves, an HRIS-driven workflow calls Admina to identify every connected service account the person holds, then runs the offboarding workflow to revoke access across the SaaS portfolio. With 57 endpoints covering users, identities, services, accounts, and workflow runs, the entire revocation can be orchestrated without manual ticket creation.

List all service accounts for the user with email leaver@example.com and trigger the standard offboarding workflow against each one.

SaaS Spend and Licence Reviews

Finance teams need a quarterly view of every SaaS subscription, who is using it, and which seats are dormant. Admina surfaces services, accounts, and identity-level usage signals through its API so a recurring report can flag licences that should be reclaimed before the next renewal.

Pull all services and their accounts, filter for accounts not used in 90 days, and produce a CSV listing the user, service, and seat cost.

Identity Hygiene and Merging

Different SaaS services use different email addresses for the same employee. Admina lets a script identify duplicate identity records and call /identity merge endpoints to consolidate them, producing a clean one-employee-one-identity dataset for IAM reporting and access reviews.

Find identities sharing the surname Tanaka with overlapping login emails and merge them into a single Admina identity record.

Compliance Evidence Export

SOC 2 and ISO 27001 audits require evidence of who has access to what. Admina's identity, account, and admin-count endpoints produce the underlying dataset that can be exported and stored as audit evidence on a defined cadence, replacing manual screenshot collection from each SaaS console.

Export the current admin user count and a per-service list of admins as a CSV for the Q2 access review folder.

AI Agent SaaS Operations

An IT operations agent uses Jentic to discover Admina endpoints, loads the schemas for users, identities, and workflows, and executes them with a vault-injected bearer token. The agent can then answer questions like 'who has access to GitHub' or run an offboarding sequence on demand without any direct knowledge of the bearer secret.

Search Jentic for 'list all users in our SaaS organisation', load the Admina /users schema, and return the first page of users with their service counts.

Key Endpoints

57 endpoints — admina by money forward is a saas management platform that consolidates identities, devices, and software licences across an organisation.

METHOD

PATH

DESCRIPTION

GET

/users

List organisation users

GET

/organization

Get the organisation profile

POST

/identity

Create an identity

GET

/identities

List identities

GET

/identities-stats

Get identity statistics

GET

/admin-count

Get the admin user count

PATCH

/user

Update a user

GET

/users

List organisation users

GET

/organization

Get the organisation profile

POST

/identity

Create an identity

GET

/identities

List identities

GET

/identities-stats

Get identity statistics

GET

/admin-count

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Admina bearer tokens are stored encrypted in the Jentic vault and attached as Authorization: Bearer at execution time. Tokens stay out of agent context and can be rotated centrally without redeploying the agent.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list SaaS users' or 'trigger offboarding') and receive the matching Admina endpoint with its full input schema, removing the need to browse Admina's reference docs.

Time to first call

Direct Admina integration: 1-2 days reading the reference, wiring auth, and handling pagination across users, identities, and services. Through Jentic: under 1 hour to search, load, and execute the first call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Okta API

Identity provider with full SCIM provisioning across SaaS, broader than Admina's discovery focus

Choose Okta when the organisation needs SSO, MFA, and SCIM provisioning as the primary identity layer rather than visibility over already-connected SaaS.

Alternative

JumpCloud API

Directory platform combining identity, device, and SaaS access management

Use JumpCloud when the team also needs device management and full directory services in addition to SaaS visibility.

Alternative

OneLogin API

SSO and access management focused on enterprise identity

Choose OneLogin when SSO and policy enforcement matter more than discovering shadow SaaS spend.

Complementary

Okta API

Pair Admina's SaaS discovery with Okta's authoritative provisioning

Use Okta as the source of truth for who exists, then use Admina to discover SaaS sprawl Okta does not yet manage.

FAQs

Specific to using Admina API API through Jentic.

What authentication does the Admina API use?

Admina uses bearer token authentication over HTTPS, scoped to a single organisation. Through Jentic the token is stored in the credential vault and attached to each request at execution time so the agent never sees the raw value.

Can I run an offboarding workflow with the Admina API?

Yes. Use the workflow endpoints to trigger a configured joiner-mover-leaver sequence against a user. Combined with /users and /identities, an agent can fetch every service account a person holds and revoke access in one orchestration.

What are the rate limits for the Admina API?

The spec does not declare explicit rate limits. Treat HTTP 429 responses as a back-off signal and retry with exponential delay; Admina enforces per-organisation throttles that depend on plan.

How do I list every user in the organisation through Jentic?

Search Jentic for 'list users in the organisation', load the schema for GET /users, and execute it. Jentic injects the bearer token; results paginate so the agent should follow the next-page link until exhausted.

Can the Admina API merge duplicate identity records?

Yes. The /identity endpoints support creating, listing, and merging identities so a single employee with several SaaS logins maps to one Admina identity. Use POST /identity for new records and call the merge operation with the source and target identity ids.

Does Admina support exporting data for audits?

The API surfaces the underlying datasets needed for audits — users, identities, services, accounts, admin counts, and identity statistics — which an agent can pull and serialise as CSV. There is no single 'audit export' endpoint; the agent assembles the evidence from these resources.