Divvy User Management API Guide

Auth method: Not documented

User object field mapping is not yet verified for this app.

Endpoint coverage is not yet verified for this app.

• Rate limits: Not documented

• Rate-limit headers: No

• Retry-After header: No

• Rate-limit notes: Not documented

• Pagination method: none

• Default page size: 0

• Max page size: 0

• Pagination pointer: Not documented

• Webhooks available: No

• Webhook notes: No publicly documented webhook system for user lifecycle events in BILL Spend & Expense (Divvy) as of research date.

• Alternative event strategy: Use IdP-driven SCIM provisioning (Okta, Entra, OneLogin) to automate user lifecycle events.

• SCIM available: No
• SCIM version: Not documented
• Plan required: Enterprise
• Endpoint: Not documented

Limitations:

• SCIM is supported only via IdP connectors (Okta, Azure AD/Entra, OneLogin); no publicly documented direct SCIM base URL or bearer token flow.
• SCIM provisioning requires Enterprise plan.
• No public SCIM API documentation found in official developer or help center docs as of research date.

The only supported automation path is IdP-driven SCIM.

For Okta: upgrade to Enterprise, generate a SCIM base URL and bearer token from Settings > Security > SSO/SCIM in the Divvy admin console, enter both into the Okta BILL Spend & Expense app provisioning settings, then enable Create Users, Update User Attributes, and Deactivate Users.

For Azure AD (Entra): follow the same token-generation step, add the BILL Spend & Expense enterprise application in Entra, set Provisioning mode to Automatic, and manually verify attribute mappings - mismatches silently fail provisioning without surfacing an error.

The SCIM bearer token is a one-time credential; if lost, it must be regenerated and re-entered in the IdP. CSV bulk import is available for adds only and does not support deprovisioning.

Automate user provisioning via Okta

1. Upgrade to Enterprise plan in BILL Spend & Expense.
2. Navigate to Settings > Security > SSO/SCIM in the Divvy admin console.
3. Generate SCIM base URL and bearer token from the admin console.
4. Enter the SCIM URL and token into the Okta BILL Spend & Expense app provisioning settings.
5. Enable 'Create Users', 'Update User Attributes', and 'Deactivate Users' in Okta.
6. Assign users/groups in Okta to trigger provisioning to Divvy.

Watch out for: The SCIM bearer token is generated once; if lost, a new token must be regenerated and re-entered in the IdP.

Automate user provisioning via Azure AD (Entra)

1. Ensure Enterprise plan is active.
2. In Divvy admin console, generate SCIM tenant URL and secret token under SSO/SCIM settings.
3. In Azure AD, add the BILL Spend & Expense enterprise application.
4. Configure Provisioning mode to 'Automatic', enter tenant URL and secret token.
5. Map attributes and assign users/groups, then start provisioning.

Watch out for: Attribute mapping between Entra and Divvy user fields must be manually verified; mismatches silently fail provisioning.

Manual user management (no API/SCIM)

1. Log in to BILL Spend & Expense admin console.
2. Navigate to People > Employees.
3. Use 'Invite Employee' to add users individually or bulk-import via CSV.
4. Assign budget, role, and card limits manually per user.

Watch out for: CSV bulk import does not support deprovisioning; offboarding must be done individually or via IdP SCIM if on Enterprise.

The primary integration trap is assuming the BILL developer API covers user management - it does not. Developers who instrument Divvy via developer.bill.com will find AP/AR endpoints with no user lifecycle surface.

A second trap is treating SCIM as a direct API: the SCIM tenant URL and token are generated inside the admin console and consumed by the IdP, not exposed as a callable endpoint for custom tooling.

There is no publicly documented webhook system for user lifecycle events, so event-driven automation outside of IdP SCIM is not supported. Teams without an Enterprise plan have no programmatic fallback and must manage users entirely through the admin console.