canonical: https://jentic.com/apis/moneyforward.com/moneyforward # Moneyforward Admina API Admina by Money Forward is a SaaS management platform that consolidates identities, devices, and software licences across an organisation. The 57-endpoint API exposes organisation users, identities and identity merging, services and accounts (the SaaS apps connected to Admina), workflows for joiner-mover-leaver automation, and exports for compliance reviews. Authentication is a bearer token over HTTPS, scoped per organisation. ## For AI 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. ## Scope Does not handle accounting, payroll, or financial transactions despite the Money Forward name - use for SaaS identity, accounts, and access management on Admina only. ## Capabilities - 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 - Export device, licence, and access reports as CSV for SOC 2, ISO 27001, and internal audits - Patch user attributes such as employment status to drive automated offboarding ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Organization** — Organisation profile and admin counts - **Users** — List, retrieve, and update employees in the organisation - **Identities** — Cross-service identity records, merge operations, and statistics - **Services and Accounts** — Connected SaaS services and per-employee account assignments - **Workflows** — Joiner-mover-leaver automations triggered against accounts ## Why Jentic - **Setup:** Wiring the Admina API by hand means managing its bearer token, targeting the itmc host, and coding the user, identity, and organization calls across a large surface yourself. Through Jentic you install once, import the Admina API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Admina carries the user and identity target in the request body rather than as a path resource, so you limit the agent to the operations it needs, such as listing SaaS users or reading identity stats. You choose the operations it may call, so a write like patching a user is not included unless you add it. - **Credential handling:** Your Admina token is stored once, encrypted, by your own Jentic One instance and injected at execution time, and can be rotated centrally without redeploying the agent. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list SaaS users' or 'trigger offboarding', and Jentic returns the matching Admina operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Okta API** — Identity provider with full SCIM provisioning across SaaS, broader than Admina's discovery focus - **JumpCloud API** — Directory platform combining identity, device, and SaaS access management - **OneLogin API** — SSO and access management focused on enterprise identity - **Okta API** — Pair Admina's SaaS discovery with Okta's authoritative provisioning ## FAQ ### 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. ### Can I limit what my agent is allowed to do with the Admina API? Yes. Because you run Jentic One yourself, you decide which Admina operations the agent may call, so you can allow read calls like listing SaaS users, listing identities, or reading identity statistics and admin counts while leaving everything else off. Admina carries the user or identity target in the request body rather than in the path, so a write such as PATCH /user or triggering an offboarding workflow is not available to the agent unless you explicitly add it. The bearer token is held by your own instance and attached at execution time, so the agent acts only within the scope your rules define.