Where to start: partner vs customer-built

Bob supports two paths for building integrations. Path A is for vendors whose customers install an app from the HiBob Marketplace. Path B is for Bob customers building something only for their own company. The paths use different sign-in models and different docs — pick one before you write code.

TL;DR

• Third-party vendor → Marketplace customers install your app: become a Marketplace partner, use OAuth, build in the Developer Portal.

• Bob customer → integrate for your own company: use a Service User, not OAuth. Start at Getting started with Bob's API.

Path A — Marketplace partner (OAuth)

Who this is for: product companies connecting their SaaS to Bob and listing in the HiBob Marketplace.

1. Apply via Become a partner.

2. After approval and T&Cs, you get a partner Bob company and Developer Portal access.

3. Follow Marketplace partner integrations.

4. Create the app with Quick start guide (OAuth, scopes, webhooks, listing).

5. Test in Dev mode: Test apps in Bob Marketplace.

Auth model: OAuth 2.0 authorization code. Customers install your app; you store tokens per Bob company. See OAuth 2.0 and Managing customer installations.

Path B — Customer-built (Service User)

Who this is for: Bob admins or internal developers automating workflows inside one Bob company.

1. Start at Getting started with Bob's API.

2. Create credentials with API Service Users.

3. Use Authorization for request auth.

4. For events, use Getting started with Webhooks (manual webhook setup in Bob — different from partner-managed webhooks).

Auth model: Service User token for your company. No Marketplace listing, no Developer Portal OAuth app.

Quick decision table