العربية

Start free trialBook a demo

Partner Program

Technology partner program: build on the API, MCP and marketplace

Connect your product to Tarleaks through the REST API, the MCP endpoints or the marketplace.

Who it suits

  • Software vendors whose product needs HR, payroll, accounting, sales or stock data.
  • Integrators who build connectors for clients and want to list them.
  • Teams building AI tools that call business systems through MCP.

What you do

  • Build a connector or app on the REST API, the MCP endpoints or the marketplace.
  • Keep it current when the API changes, and support your own customers.
  • Ask only for the permissions your app needs.

What we provide

  • A sandbox workspace to test against.
  • API and MCP documentation in the developer reference.
  • A security review of your integration.
  • A marketplace listing, featured first in the countries you choose.

What you need

  • A legal entity.
  • An OAuth app that uses PKCE.
  • A short security review.

How you earn

A marketplace listing and a joint announcement. Revenue share applies only if it is agreed.

Revenue share, if any
Set in your partner agreement

Your first steps

  1. Apply

    Choose Technology and describe your product and the integration you have in mind.

  2. Manual review

    We read your application and your product details.

  3. Security review

    A short review of how your integration handles data.

  4. Build and test

    Work in your sandbox workspace.

  5. Listing

    We add your listing to the marketplace by hand.

How listing works

This is how the marketplace works today. It is curated, not self-service.

  1. Listings are added by hand

    In this first phase, a Tarleaks administrator adds and publishes each listing. Self-service listing is planned, not available yet.

  2. Install with OAuth and PKCE

    A company administrator installs your app through an OAuth consent flow that uses PKCE.

  3. Scopes map to our permissions

    The scopes you ask for must map onto existing Tarleaks permissions. The company administrator approves them, and they are never widened without a new approval.

  4. Short-lived tokens

    Your backend exchanges its credentials for a short-lived token that carries only the granted scopes.

  5. Audited and revocable

    Installs, revocations and token exchanges are recorded and visible to the company administrator, who can revoke an install at any time.

Read the developer reference

Questions about this track

Can I list my app myself?

Not yet. Listings are added by hand in this first phase.

Where is the API documented?

In the developer reference on this site: the REST API, the MCP endpoints and API tokens.

Do you take a revenue share?

Only if it is agreed. It is set in your partner agreement.

Do I need a legal entity?

Yes. A listing names the legal entity that owns the app, and its country.

Can my app use customer data freely?

No. It receives only the scopes the company administrator approved.

Other tracks

Ready to partner with us?

Apply in a few minutes. We reply by e-mail.