Prerequisites
Fleetshare can only be used after you have applied and been accepted into the supplier program. The entire application and onboarding runs through the EarnFM Supplier Portal.
EarnFM Account
Before you can start, you need an account on EarnFM. You can create one at app.earn.fm. The supplier portal uses the same login: open suppliers.earn.fm (or go to app.earn.fm/#/redirect-suppliers) and you are signed in automatically with your EarnFM account.
More than 20 Active IP Addresses
The supplier program is intended for partners bringing 20 or more IP addresses (application users, servers, or devices). If you have fewer than that, you don’t need the SDK — simply use the regular EarnFM app to share your own connections.
Apply in the Supplier Portal
Open the Supplier Portal and submit an application. Select your integration type (SDK integration, Fleetshare server, or Docker), describe your setup, and — for SDK integrations — list the websites of the products/apps that will embed the SDK. Our team reviews every application; you will be notified by email once it is accepted.
Complete Onboarding
After acceptance, the portal walks you through the remaining onboarding steps. Both must be completed — suppliers without them may not be able to share additional IPs, and payouts can be withheld:
1. KYC Verification
You verify your identity directly in the portal (powered by Didit). Individuals go through an ID + address verification; companies go through a business (KYB) verification. Click Verify identity on your supplier dashboard and follow the hosted flow.
2. Sign the Supplier Agreement
The supplier agreement is generated and signed fully online. Once your profile (company/individual details, address, and for SDK suppliers your product websites) is complete, click Sign contract on the dashboard, sign in the browser, and press Check status — done. No emails or paperwork needed.
API Key
To run the SDK you need your EarnFM API key. You can find it on your EarnFM dashboard in the Settings.
User Consent
Every device running the SDK needs a recorded user consent — see User Consent and the Consent API. Devices without a granted consent are not able to connect.