TalentLayer Documentation
  • 👋Introduction
    • Value Proposition
    • Options for Integration
      • On-Demand Integration
      • Native Integration
    • TalentLayer's Functions
      • PlatformID
        • Fees & Economics
      • TalentLayerID
      • Reviews
      • Services
      • Escrow and Dispute
        • Dispute Workflow
        • Arbitration
          • Kleros Arbitration
          • Platform Managed Arbitration
    • Current Network Liquidity
    • Decentralization
  • ⚙️Technical Guides
    • Web 3 SDK & API
    • StarterKit Template
    • Technical Schemas
    • Network Support
    • Lower-Level Guides
      • Smart Contracts
        • Deployments
        • TalentLayerPlatformID.sol
        • TalentLayerID.sol
        • TalentLayerService.sol
        • TalentLayerReview.sol
        • Escrow & Dispute Contracts
      • The Graph
        • Introduction
        • Querying from an application
        • Queries examples
        • Implementing the pagination
      • Metadata
      • Third-Party Modules
        • Lens Protocol - Social
        • XMTP - Messaging
        • Sismo - Privacy
        • Iexec - Web3Mail
      • Messaging
        • Integrating XMTP
      • Standards
        • ERC-792: Arbitration standard
        • ERC-1497: Evidence Standard
      • How-To Guides
        • How to implement minting TalentLayer IDs?
        • How to implement the service creation?
        • How to implement the proposal creation?
        • How to implement the proposal validation?
    • Delegation
      • Meta Transaction
      • Delegate System
        • Setting
        • User workflow
        • Service creation example
        • How mintForAddress works
  • ⭐Get a Platform ID
  • 🧠Inspiration for Builders
  • 💬Contact The Team
  • 🦝Core Developer Guides
    • Subgraph Local Setup
    • Smart Contracts Local Setup
    • Advanced Documentation
    • Contract & Graph Deployment Guide
    • TalentLayer Improvement Proposals
    • Audit Report
Powered by GitBook
On this page

Was this helpful?

  1. Introduction
  2. Options for Integration

Native Integration

TalentLayer as a Backend

Platforms that choose Native Integration opt to use TalentLayer as a backend for their platform, where all supply and demand is listed at the network level for cross-platform deals.

Native Integration is good for teams who may:

  • want to have 100% of their current supply and demand listed on the network for cross-platform transactions

  • don't have an existing user account system, payments system, or dispute resolution

  • are adding marketplace features into an app in a different vertical

  • don't want to custody user data for GDPR reasons

  • want to avoid building a backend from scratch, to go to market faster

All of your users and service requests will be listed on the network as available supply and demand; any other platform on the network can propose cross-platform transactions with your users.

With Native Integrations, each user on your platform has an reputation and profile at the network level that can be viewed by and used on other platforms.

Native Integration is available today, with extensive documentation, code examples, and more.

PreviousOn-Demand IntegrationNextTalentLayer's Functions

Last updated 1 year ago

Was this helpful?

👋