Users can share their personal account data by inviting team members and assigning them particular roles (Admin, Finance Manager, Accountant, and Approver). Each role comes with specific permissions, which you can find in our FAQ.

The user holding the account's data is called the organization owner and has the same set of permissions as any other admin. The owner of an organization cannot change by design.

To summarize, each user owns a personal account. As soon as they share it with other users by inviting them, it essentially creates an Organization.

Listing Organizations

The following endpoint retrieves the list of organizations a user belongs to. This list does not include the user's account (personal account) but only external organizations that they have been invited to.

Important: This endpoint is only available with the OAuth authentication scheme, not API keys. You need to ask for the user:read OAuth scope when retrieving a token in order to have access to this endpoint.

List organizations the user belongs to


    "id": "654b9aaefb9eb1ddde2cf85f",
    "name": "acme-org",
    "displayName": "Acme Org",
    "role": "admin",
    "owner": {
      "id": "654b9aaa00137146c4fd7e54",
      "email": "",
      "firstname": "Bills",
      "lastname": "AcmeOrg"

Accessing an Organization's Data

When querying Request Finance's API with a user's OAuth token, you will retrieve the user's personal account data.

To access data from an Organization this user belongs to, add the following header to each API call:

X-Organization: [ID]

Use the Listing Organizations API endpoint to retrieve the proper organization ID. For instance:

X-Organization: 654b9aaefb9eb1ddde2cf85f

If the user is the owner of the organization, you don't need to add the X-Organization header. Their personal account itself constitutes the organization; accessing the user's data is like accessing the organization's data.

Last updated