The Bill.com Developer Platform lets you interact with the Bill.com service through easy-to-use APIs, enabling you to automate the actions that a Bill.com user would perform through our application. This documentation walks you through various aspects of the platform, to get you started on building a high-quality integration with Bill.com.
Developers are independent of organizations or users within the Bill.com system, and would register with Bill.com in order to provide an integration with another application or value-added service in addition to the Bill.com service. Each developer is identified by a unique Developer Key, which needs to be passed with every API call.
Organizations are the entities that reflect real-world businesses. An organization may have one or more users with access to the various functions within the organization (such as creating bills, approving bills, making a payment, etc). Performing an operation for a specific organization is achieved by creating a login session with username, password, and organization ID (a unique identifier which is required for most API calls), and passing the session ID with each operation.
One or more users can access an organization, and one user can have the same login credentials associated with more than one organization. TTherefore, both the user and the organization need to be passed on every API call, so we know which user is performing the operation, and in which organization to perform the operation. This is achieved by creating login session with user name, password and organization id and passing the session id with each operation. For API calls only, the user login credentials can be replaced by a Token name and password. A Token can be created generated on the Bill.com application and can only be used for API calls. Entity
Entity is a Business Object in the Bill.com system that is acted upon to achieve a certain objective. For example, to make a bill payment, you need an entity of a type Vendor that is getting paid, an entity of type Bill that is being paid, and an entity of type SentPay for the payment.
See what's included in the development
For more info and support, contact us!