canonical: https://jentic.com/apis/bill.com/organization-basic-operations # Bill Organization | Basic operations Jentic publishes the only available OpenAPI specification for Organization | Basic operations, keeping it validated and agent-ready. This BILL surface manages the foundational records of an organisation: the organisation itself, its users and profiles, attached documents, internal messages, bank accounts, money-movement records, and card accounts. Agents use it to provision users, read profiles and permissions, fetch documents attached to transactions, and inspect bank balances and money-movement history. It is the administrative spine that supports every AP and AR workflow. ## For AI agents Provision users, manage profiles and permissions, read bank balances and money-movement records, and fetch documents inside a BILL organisation. ## Scope Does not handle invoicing, vendor payments, or chart-of-accounts setup - use for BILL organisation administration, users, documents, and bank balance reads only. ## Capabilities - Provision and update user accounts with profile and permission assignments - Read organisation, profile, and permission records to audit who can do what - Fetch document pages and document metadata attached to BILL transactions - Send and list internal messages tied to organisation activity - Inspect bank account configuration, current bank balance, and money-movement history ## Use cases ### User provisioning and offboarding Add new finance team members to a BILL organisation, assign their profile, and soft-delete leavers. The API exposes Crud/Create/User and Crud/Update/User for individual changes, plus Bulk/Crud variants for batch onboarding. Crud/Delete/User and Crud/Undelete/User keep the audit trail intact while removing day-to-day access. Example prompt: Create a new User with email finance.new@example.com assigned to the AP Approver profile, then verify by calling Crud/Read/User ### Permission audit Pull the full permission matrix to confirm who can approve bills, send invoices, or move money. List/Profile and GetProfilePermissions return profile definitions and their associated permissions, while List/User maps users to profiles. A compliance agent can run a quarterly access review without exporting CSVs from the BILL UI. Example prompt: Call List/Profile, then GetProfilePermissions for each profile, and return a list of users by profile from List/User ### Bank balance and money-movement reporting Read connected bank balances and the money-movement ledger to feed cash-flow dashboards. GetBankBalance returns the current balance for a configured BankAccount, and List/MoneyMovement enumerates payments in flight. Agents use this to answer 'how much cash do we have to disburse this week?' without opening BILL. Example prompt: Call GetBankBalance for each configured BankAccount and return the aggregate balance, then call List/MoneyMovement for the last 7 days ### Document retrieval for AP review Fetch invoice scans and supporting documents attached to BILL transactions. GetDocuments returns metadata for documents tied to a record, and GetDocumentPages returns the page-level images. An AP review agent can pull a vendor invoice scan into a verification pipeline before approving payment. Example prompt: Call GetDocuments for a target Bill ID and then GetDocumentPages to retrieve the first page image of the linked invoice ### Agent-driven org administration via Jentic An AI agent uses Jentic to discover organisation operations from intents like 'add a user to BILL' or 'check our bank balance'. Jentic returns the matching operation, loads its schema, and executes with credentials from the vault. The agent can administer a BILL organisation without ever holding raw session tokens. Example prompt: Search Jentic for 'add a user in bill.com', load the Crud/Create/User schema, and execute it for a new finance hire ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /Crud/Read/Organization.json | Read the organisation record | | POST | /Crud/Create/User.json | Create a user account | | POST | /Bulk/Crud/Create/User.json | Bulk create user accounts | | POST | /List/Profile.json | List permission profiles | | POST | /GetProfilePermissions.json | Get permissions on a profile | | POST | /GetBankBalance.json | Get the current bank balance | | POST | /List/MoneyMovement.json | List money-movement records | | POST | /GetDocuments.json | Fetch documents attached to a record | ## Key resources - **Organization** — Read the parent organisation record - **User** — Full CRUD, bulk, and undelete operations on user accounts - **Profile** — Read and list permission profiles - **BankAccount** — Read and list configured bank accounts and their balances - **MoneyMovement** — Read and list money-movement records - **CardAccount** — List linked card accounts - **Document** — Fetch document metadata and page images - **Message** — Send and list internal organisation messages ## Why Jentic - **Setup:** Wiring the BILL organization basic-operations API by hand means logging in for a broad organisation-level session id, pairing it with your developer key on every RPC-style POST, and shaping each user, profile, and document body yourself. Through Jentic you install once, import this BILL API from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** This API carries its identifiers in the request body of RPC-style operations rather than the URL path, so limit the agent to the operations it needs, such as reading the organisation or checking the bank balance. You choose that set, so creating users or reading documents is not reachable unless you include them. - **Credential handling:** Your BILL developer key and organisation-level session token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'add a user to BILL' or 'check our BILL bank balance', and Jentic returns the matching organisation operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **BILL Organization Accounts Tracking** — Tracking dimensions live alongside organisation administration. - **BILL AP Vendor Transactions** — Vendor transactions consume bank balances and documents managed here. - **Xero Accounting** — Xero exposes a similar user, organisation, and bank-feed surface at the ledger level. ## FAQ ### Why is there no official OpenAPI spec for Organization | Basic operations? BILL does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Organization | Basic operations 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 Organization Basic Operations API use? BILL uses an API key plus session token model. Agents log in once to obtain a session token and pass it on each call alongside the developer key. Jentic stores both encrypted in the vault and the agent only ever holds a scoped reference. ### Can I provision new users with this API? Yes. Call POST /Crud/Create/User.json to add an individual user, or POST /Bulk/Crud/Create/User.json for batch onboarding. Assign permissions by referencing a profile ID returned from POST /List/Profile.json. ### How do I check our bank balance through Jentic? Search Jentic for 'check bill.com bank balance'. Jentic returns the GetBankBalance operation, loads its schema, and your agent calls POST /GetBankBalance.json with the target BankAccount ID. Pair with POST /List/BankAccount.json to enumerate accounts first. ### What rate limits apply to this API? BILL applies per-organisation throttling. Specific quotas are not exposed in the spec, so prefer POST /Bulk/Crud/Create/User.json over looped single-create calls when onboarding multiple users. ### Is the Organization Basic Operations API free? API access is bundled with paid BILL plans rather than a separate free tier. You need an active BILL organisation and a developer key. Jentic does not add usage charges on top. ### Can I limit what my agent is allowed to do with the BILL Organization Basic Operations API? Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations and credentials the agent may use. Every call here is an RPC-style POST that carries its identifiers in the request body, so you allow only the operations the task needs, such as reading the organisation with Crud/Read/Organization or checking the balance with GetBankBalance. Operations you leave out, like Crud/Create/User or GetDocuments, are simply not reachable by the agent.