Platforms that choose On-Demand Integration opt to use TalentLayer to supplement existing supply and demand on their marketplace.
On-Demand Integration is good for teams who may:
want to list only excess supply and demand on the network for cross-platform transactions
already have an existing user account system, payments system, or dispute resolution
want to maintain custody of their own user's profiles and their current network effect
When you lack supply or demand for a specific category of service, you can pull in resources from the network on demand.
On-Demand Fulfillment Workflow
Marketplace A has insufficient supply of Python developers to meet the demand of Python gigs available on their platform.
Marketplace A pushes current available Python gigs to the network via TalentLayer API.
Marketplace A receives proposals from users across the network, which it then displays to the hirers on it's platform.
Hirers select the winning candidate and complete the transaction. Payment remittance is triggered on Marketplace A by the hirer and facilitated by TalentLayer.
The candidate receives payment on the platform they are using.
All of your users and service requests will remain custodied by your platform in whatever manner they are today. There will be no network-native representation of your users available for other platforms to view or display.
On-Demand Integration is a feature of the TalentLayer Abstracted API and SDK. While it is possible to build a platform with On-Demand Integration today, this implementation pattern is not documented and has no example code available.