The Real Cost of Partner Onboarding: 385 Staff Hours per API Agreement
Partner onboarding costs a median 385 staff hours per API agreement. See where the hours go, how to calculate your own cost and which steps to automate first.
.png)
TL;DR
Partner onboarding for API access costs a median of 385 staff hours per agreement, according to the US Consumer Financial Protection Bureau (CFPB).
At the CFPB's estimate of $89.99 an hour, that's about $34,600 for each partner, before a single API call.
Most of those hours go to contracts, security checks, manual credential setup and integration support. Automate credentials, sandbox access and standard approvals first. Keep people on contracts, KYC and custom terms.
Count the people who touched your last partner integration: legal, security, the gateway team, the engineer who created the key. Then count the weeks between the signed contract and the partner's first API call.
Most teams have never counted either, because the work is spread across five departments and no single budget. This guide shows what partner onboarding costs, where the hours go, how to calculate your own number and which steps to automate first.
How much does partner onboarding cost?
API partner onboarding costs a median of 385 staff hours per agreement, or about $34,600 in staff time. That's the US benchmark from the CFPB's open-banking rule, the most detailed public measurement of what it takes to give an outside company access to an API. The cost sits across legal, security, product and engineering teams, so it rarely shows up as one line in a budget.
What is API partner onboarding?
API partner onboarding is defined as the process of taking an outside company from a signed agreement to a working, approved connection to your APIs. It covers contracts, security and compliance checks, credentials, sandbox and production access, integration support and go-live approval.
What does it cost to sign one API data-access agreement?
In its final rule on personal financial data rights, published in November 2024, the CFPB cited data aggregators' estimates of the time it took to negotiate a data-access agreement with a bank. The answers ranged from 50 to 4,950 staff hours. The median was 385 hours.
The CFPB lists who those hours belong to: business relationship managers, software developers, lawyers, compliance professionals and senior management. Using the CFPB's estimated total hourly compensation of $89.99, 385 hours comes to about $34,600 per agreement. The 2023 proposed rule used $85.26 an hour, which gives about $32,800.
Why the 385-hour benchmark applies beyond open banking
The CFPB measured US open-banking agreements, but the work it describes is the same for any company that gives partners access to APIs: contracts, security reviews, credentials and integration support. Payments providers, insurers, healthcare platforms and telecoms run the same steps with the same roles.
Treat 385 hours as a reference point, not a rule. Two caveats apply:
- The range is wide: Simple partnerships take far less time, and complex ones take far more. The top of the range is nearly 5,000 hours.
- The rule itself is under review: The CFPB reopened the rule for reconsideration in 2025. The survey data on onboarding hours is still the best public measurement available.
How long does API partner onboarding take?
API partner onboarding takes weeks for a simple sandbox connection and months, sometimes more than a year, for a regulated production partnership. Staff hours don't map one-to-one to calendar time. Most of the delay is waiting: for a contract review, a security sign-off or an engineer to create credentials.
Why do some partner integrations take more than a year?
Partner integrations stretch past a year when every step waits on a different team and nothing runs in parallel. Two examples from our conversations with API teams, anonymized:
- A European bank: Partner onboarding takes more than a year from first conversation to production access.
- A healthcare company: Partners are onboarded from a Word document, and an engineer creates every API key by hand.
Neither team is unusual. The pattern is the same: the API is ready, but access depends on email, tickets and one person who knows how to set up a key.
Where do the hours go in the partner onboarding process?
The hours in the partner onboarding process go to five stages: contract and legal review, security and due diligence, credential setup, integration support and go-live approval. Contracts and security take the most time. Credentials and support take the most avoidable time, because they repeat for every partner.
The table splits the CFPB's 385-hour median across those five stages. The split is our illustrative model, based on the roles the CFPB lists, not CFPB data.
| Stage | Who's involved | Typical work | Illustrative hours | Can it be automated? |
|---|---|---|---|---|
| Contract and legal review | Lawyers, relationship managers | Negotiate terms, data use, liability | 120 | Partly, with standard terms |
| Security and due diligence | Security, compliance | Questionnaires, KYC, risk review | 90 | Partly, with standard tiers |
| API key and credential setup | Developers, gateway team | Create apps, keys, scopes, sandbox access | 60 | Yes |
| Partner integration testing and support | Developers, support | Answer questions, debug, review test calls | 85 | Mostly, with docs and sandbox |
| Go-live approval | Senior management, product | Sign off production access | 30 | Partly, with approval workflows |
| Total | 385 |
Contract and legal review
Contracts take the longest because every partner starts from a blank page. Standard terms for each access tier, such as sandbox, standard production and premium, cut the negotiation down to exceptions.
Security and due diligence checks
Security teams send questionnaires and run KYC (know your customer) checks before granting production access. These checks are necessary, but they're often repeated for low-risk access, such as sandbox keys, that doesn't need them.
API key and credential setup
Credential setup is the most repetitive stage. An engineer creates an app, generates a key, sets scopes and sends it over email or chat, for every partner and every environment. This is the step the healthcare company above still runs by hand.
Partner integration testing and support
Partners ask the same questions: which API to use, why a call fails, where the sandbox is. Accurate docs and a realistic sandbox answer most of them without an engineer. Our guide to self-serve sandbox APIs covers how to set one up.
Go-live approval
Production access usually needs a manager's sign-off. When approvals happen in email, they wait in inboxes. When they happen in a workflow with the partner, plan and test results attached, they take minutes.
How do you calculate your partner onboarding cost?
Your partner onboarding cost is your staff cost per partner plus the revenue you lose while partners wait. Most teams only count the first part. The second part is often larger, because every month of onboarding is a month the partner isn't paying or transacting.
The partner onboarding cost formula
Use two lines:
- Staff cost = Staff hours per partner × loaded hourly rate × partners per year
- Delay cost = Monthly revenue per partner × months from contract to first production call × partners per year
Total partner onboarding cost = Staff cost + delay cost
If you don't track hours per partner, start with the CFPB median of 385 and adjust once you have your own numbers.
Worked example: the cost of onboarding 20 API partners a year
The inputs below are illustrative. Replace them with your own.
| Input | Value |
|---|---|
| Partners onboarded per year | 20 |
| Staff hours per partner | 385 (CFPB median) |
| Loaded hourly rate | $90 |
| Staff cost per year | $693,000 |
| Monthly revenue per live partner | $10,000 |
| Months from contract to first call | 6 |
| Delay cost per year | $1,200,000 |
| Total partner onboarding cost per year | $1,893,000 |
In this example, delay costs more than staff time. Cutting onboarding from six months to one saves $1,000,000 a year in delayed revenue, before you count a single staff hour.
The hidden API integration cost: delayed revenue
Delayed revenue is the API integration cost that never appears in a budget. Finance sees salaries, not the partner who went live in July instead of February. Track time to first production call for every partner, and you'll see the cost the staff-hours number misses. Our guide on cutting time to first call covers how to measure it.
Partner onboarding checklist: what to automate first
Automate the steps that repeat for every partner and carry little risk: credentials, sandbox access, standard approvals and docs. Keep people on the steps that carry legal or financial risk: contracts, KYC and custom terms. The CFPB itself expects standardization to cut the 385-hour median to about 120 hours, a drop of nearly 70%.
Automate first: credentials, sandbox access and standard approvals
- Self-service sign-up: Partners create an account and an app without a ticket.
- Instant sandbox keys: Sandbox credentials are issued automatically, with test data ready.
- Production keys through your gateway: Production credentials are created once access is approved, not by an engineer on request.
- Approval workflows for standard tiers: Requests go to the right approver with the partner and plan attached, instead of to a shared inbox.
- Self-service key rotation: Partners rotate and revoke their own keys.
- Docs and API discovery: One catalog shows partners which APIs they can use.
- Usage dashboards: Partners see their own calls and errors, which cuts support questions.
Keep a human on contracts, KYC and custom terms
- Contracts: Use standard terms per tier, but keep legal review for exceptions.
- KYC and due diligence: Keep checks for production access to sensitive data.
- Custom commercial terms: Volume deals and non-standard pricing need a person.
This is right for you if you onboard more than a handful of API partners a year, credentials are created by hand, or partners wait weeks for production access.
This is not right for you if you have one or two strategic partners on a fixed integration. At that volume, a dedicated onboarding call is cheaper than automation. For the full list of tasks partners should finish alone, see our guide to the self-service API portal.
How does self-service API onboarding cut partner onboarding time?
Self-service API onboarding cuts partner onboarding time by removing the waits between teams. Partners sign in, see the APIs their contract covers, request access and get credentials from your gateway as soon as an owner approves. The repeated work, credential setup and routine support, drops out, and approvals happen in minutes instead of inboxes.
What partner onboarding looks like with DigitalAPI
Teams using DigitalAPI replace the email-and-ticket process with one self-service flow across every gateway they run:
- Sign in: The partner signs in through your identity provider with SAML or OIDC single sign-on.
- Browse: They see only the APIs and plans their role allows.
- Request: They subscribe to a plan. Sandbox plans can approve themselves, and production plans go to an owner for review.
- Approve: The owner approves in one click, with the partner and plan attached.
- Call: DigitalAPI creates the key in your gateway, and the partner makes a first call from the built-in console.
Against the 385-hour model, this flow targets the stages that repeat for every partner: credential setup, routine support and go-live approval. Contracts and KYC stay with your team.
See how many hours your next partner could skip:
Book a DigitalAPI demo!
Partner onboarding FAQs
How long does partner onboarding take?
API partner onboarding takes from a few weeks for a sandbox connection to more than a year for a regulated production partnership. The CFPB reports a median of 385 staff hours to negotiate one data-access agreement. Most calendar time is spent waiting on contract reviews, security sign-offs and manual credential setup.
How much does it cost to onboard an API partner?
The CFPB's 2024 final rule puts the median at 385 staff hours per data-access agreement, or about $34,600 at its estimated $89.99 an hour. Add delayed revenue: every month a partner waits for access is a month they aren't paying or transacting.
What slows down the partner onboarding process?
The partner onboarding process slows down when each step waits on a different team: legal for the contract, security for due diligence, an engineer for credentials and a manager for go-live approval. Manual credential setup and email-based approvals cause most of the avoidable delay.
How do you reduce partner onboarding time?
You reduce partner onboarding time by automating the steps that repeat for every partner: sign-up, sandbox keys, production credentials, standard approvals and key rotation. Use standard contract terms per access tier, and keep human review for KYC and custom deals. The CFPB expects standardization to cut onboarding from 385 to about 120 staff hours.
What should a partner onboarding checklist include?
A partner onboarding checklist should include contract and data-use terms, security and KYC checks, app registration, sandbox credentials, documentation, integration testing, production approval, production credentials, key rotation and usage monitoring. Mark which steps are automated and which need a person, and track time to first production call.
What is the difference between partner onboarding and API onboarding?
Partner onboarding covers the whole relationship with an outside company, including contracts, due diligence and commercial terms. API onboarding is the technical part: getting a developer from sign-up to a working API call with credentials, docs and a sandbox. API onboarding is usually the part you can automate most.
Final word: what does partner onboarding cost you?
Partner onboarding costs a median of 385 staff hours per API agreement, and most of that cost is invisible because no single team owns it. Count your hours, count your months to first call, and you'll know your number. Then automate the steps that repeat for every partner, and keep your people on the decisions that need them.
Learn how API teams cut onboarding from months to days
See it with your own gateways in a DigitalAPI demo.
Dhayalan Subramanian is Associate Director, Product Growth at DigitalAPI, where he leads go-to-market and product growth for the company’s multi-gateway API management platform. His work focuses on helping large enterprises and mid-market cloud companies consolidate APIs across AWS, Azure, Apigee, Kong, MuleSoft, and other gateways into a single control plane for governance, discovery, monetization, and agent consumption.
Dhayalan brings 14+ years of experience across product strategy, enterprise architecture, and engineering leadership. Earlier in his career, he held senior roles at Encora (as Associate Architect and Technical Manager), Mindtree (Technology Lead), Tech Mahindra (Technical Lead), and Primus Analytics, where he designed integration frameworks and delivered enterprise-grade digital platforms for global customers.
At DigitalAPI, he works directly with platform, integration, and developer experience leaders at Fortune 500 organizations to operationalize unified API catalogs, developer portals, and MCP-ready APIs. He writes regularly on API developer experience, API governance, and AI agent architectures.
One email a fortnight. Worth opening.
A short digest of what we're writing, what we're learning from customers, and the handful of links you'd actually want from us. No tracking pixels.
.avif)
