> ## Documentation Index > Fetch the complete documentation index at: https://docs.proofage.net/llms.txt > Use this file to discover all available pages before exploring further. # Identity verification on Sharetribe > Add identity verification to a Sharetribe marketplace without code: ProofAge and Zapier email new users a verification link and approve verified users. This guide adds identity verification to a [Sharetribe](https://www.sharetribe.com) marketplace without code. New users get a verification link by email, and verified users are approved or given posting and transaction rights automatically. It is written for marketplace operators: everything happens in Sharetribe Console, the ProofAge console and Zapier. Typical uses: * **Service marketplaces** (home services, tutoring, childcare, coaching) can ask providers to verify before they publish a listing. * **Rental and peer-to-peer marketplaces** (vehicles, equipment, spaces) can ask customers to verify before they book. * **Age-restricted marketplaces** can confirm that users are old enough before they buy or sell. The setup has three building blocks: your marketplace's **access control** settings, a ProofAge workspace, and the [ProofAge app for Zapier](https://docs.proofage.net/integration/zapier.md), which connects the two. This page explains how the pieces fit together, how to go live and what to check when something doesn't work. The step-by-step instructions, with screenshots, are on two pages: > [card] [1. Send the verification link](https://docs.proofage.net/integration/sharetribe/send-verification-link.md) > > Set up your marketplace and ProofAge, then build the Zap that emails every new user a link. > [card] [2. Grant access after verification](https://docs.proofage.net/integration/sharetribe/grant-access.md) > > Build the Zaps that approve verified users and email declined ones, then test every case. ## What you need | | What for | Cost | | - | - | - | | **Sharetribe marketplace** | Your marketplace. Start in your **Test** environment. | Any plan | | **Zapier account** | Runs the automations ("Zaps"). | The Zaps in this guide have more than two steps, so they need the **Professional** plan or higher. A new Zapier account starts on the Free plan; you can start a free 14-day Professional trial from **Settings → Billing & usage → Try Pro for 14 days**. No card is needed. When the trial ends, the Zaps stop unless you upgrade. | | **ProofAge account** | Checks the ID document and the selfie. Sign up at [app.proofage.net](https://app.proofage.net). | Free trial verifications with no card, then a price per check: see [Pricing](https://docs.proofage.net/getting-started/pricing.md). Test workspaces are always free. | | **Email account** connected to Zapier (Gmail, Outlook or similar) | Sends users their verification link and the result. | Free | Each verified user uses 6 Zapier tasks and each declined user 4 (one per action step that runs; trigger and filter steps are free). ## How it works The setup uses three Zaps: ``` Zap 1 – Send verification link Sharetribe: new user signs up → ProofAge: create a verification (linked to the user's Sharetribe ID) → Email: send the user their verification link The user opens the link, scans their ID and takes a selfie. ProofAge checks the document, matches the face and checks liveness. Zap 2 – Approve verified user ProofAge: verification approved → Sharetribe: look up the user → Sharetribe: approve the user and/or grant permissions → Email: tell the user they're verified Zap 3 – Email declined user ProofAge: verification declined → Sharetribe: look up the user → Email: tell the user, with a link to your "verification failed" page ``` ProofAge sends results to Zapier **instantly**, so a verified user gets access a few seconds after the decision. The only wait is at the start. Zapier checks Sharetribe for new users on a schedule (every 2 minutes on the Professional plan these Zaps need), so the verification email arrives within 2 minutes of sign-up. The result is never shown on the verification screens themselves. When the person finishes, ProofAge always sends them to the same "we've received it" page, and the result arrives by email. That way nobody can try the check over and over to learn what gets through. ## 1. Set up your marketplace ### 1.1 Access control Decide what new users can do before they are verified. In Sharetribe Console, go to **Build → General → Access control** and tick the options you want. For example: * **Approve users who want to join.** New users can't do anything until they are approved. Zap 2 approves them as soon as ProofAge verifies them. * **Restrict posting rights** and/or **Restrict transaction rights.** New users can sign up and browse, but can't post listings or start transactions until Zap 2 grants these permissions. ### 1.2 Content pages With the Pages editor, create two simple pages. One section with a title and a paragraph is enough for each: * **Verification received** (`verification-received`): where ProofAge sends users after the last verification screen. It thanks them and says the result will arrive by email. It must not say that the verification succeeded, because the result isn't known yet. * **Verification failed** (`verification-failed`): linked from the email users get when their verification is declined. It explains what to do next, such as replying to ask for a new link. There is no "verification successful" page. The email that tells users they're verified links straight to your marketplace. ## 2. Set up ProofAge Create a ProofAge account at [app.proofage.net](https://app.proofage.net) and create a **test workspace**. A workspace holds your verification settings: which check runs (ID document with selfie and liveness, or selfie age estimation), the minimum age, and where users go after the last screen. In a test workspace nothing is charged and you choose each result yourself, so you can test every scenario without a real ID. Then connect ProofAge to Zapier. You don't need to copy API keys: Zapier asks you to sign in to ProofAge and choose a workspace. > [!NOTE] > > The ProofAge app for Zapier is in beta and available through an invite link, which the first step page gives you. Once it is listed in Zapier's App Directory, you'll find it by searching for "ProofAge". ## 3. Connect ProofAge and your marketplace with Zapier ### 3.1 Send a verification link when a user signs up The first Zap starts when a new user joins your marketplace (**Sharetribe → User Events → User created**). It creates a verification in ProofAge (**ProofAge → Create Verification**), with the user's Sharetribe ID as the **External Reference**, so the result can be matched to the right account later. Then it emails the user the verification link. Full steps: [Send the verification link](https://docs.proofage.net/integration/sharetribe/send-verification-link.md). ### 3.2 Grant access after a successful verification The second Zap starts when ProofAge approves a verification (**ProofAge → Verification Completed**, Status **Approved**). It uses the External Reference to find the user in Sharetribe, then approves the user (**Sharetribe → Approve User**) and/or grants them permissions (**Sharetribe → Update Permissions**) and sends a confirmation email. A third, shorter Zap does the same for declined verifications: it emails the user a link to your "verification failed" page. Full steps: [Grant access after verification](https://docs.proofage.net/integration/sharetribe/grant-access.md). ## 4. Go live First test the whole flow in your Test environment, as described in [Test the whole flow](https://docs.proofage.net/integration/sharetribe/grant-access.md#test-the-whole-flow). When everything works in Test: 1. In Sharetribe Console, create an Integration API application in your **Live** environment and add a second Sharetribe connection in Zapier with its keys. 2. In ProofAge, create a **live** workspace with the same settings and add a second ProofAge connection in Zapier for it ("*Workspace name* (Live)"). 3. In each Zap, switch every Sharetribe and ProofAge step to the live connections. 4. Replace the Test addresses with your live domain: the **Redirect URL** in Zap 1, the links in the emails of Zap 2 and Zap 3, and the **Redirect URL** of the live workspace. 5. Publish each Zap. Keep the test connections: they're useful for trying out changes later. ## Troubleshooting The ProofAge console shows every verification and whether its result reached Zapier, and Zapier's Zap history shows every run. Start there. | Problem | Likely cause and fix | | - | - | | The verification email doesn't arrive after sign-up | Zapier checks Sharetribe on a schedule; wait up to one polling interval. Check that Zap 1 is on and connected to the right environment (Test or Live). | | Zap 1 fails on Create Verification with a billing error | Your live ProofAge workspace has used its free verifications and has no payment method. Add billing in the ProofAge console, or test with a test workspace. | | "ProofAge no longer accepts the key this connection uses" | The "Zapier · …" key was deleted in the ProofAge workspace. Reconnect ProofAge in Zapier. | | "This workspace already has 5 secret keys" when connecting | Delete a key you no longer use in the ProofAge console, then connect again. | | Connecting ProofAge is refused | Only ProofAge administrators and developers can connect. Ask an administrator for that role. | | Zap 2 doesn't run after approving a test verification | Check that the trigger's Status is **Approved** and that the Zap uses the same ProofAge workspace you approved the verification in. | | Approve User fails | The user isn't pending approval: either your marketplace doesn't require approval to join (remove the step and use Update Permissions), or the user was already approved. | | Show User finds no user | The External Reference isn't a Sharetribe user ID, or the Sharetribe connection points to the other environment. Zap 1 must map **User Id** to External Reference. | | A live verification shows **Review** in ProofAge | ProofAge wants a person to look at it. Decide it in the ProofAge console; Zap 2 or 3 runs when you do. | | The user says the link expired | Links expire 7 days after they're created. Send a new one: see [Let a user try again](https://docs.proofage.net/integration/sharetribe/grant-access.md#let-a-user-try-again). | ## Related * [Zapier](https://docs.proofage.net/integration/zapier.md): everything the ProofAge app for Zapier can do. * [Test workspaces](https://docs.proofage.net/integration/sandbox-testing.md): how test mode works and how outcomes are set. * [Verify marketplace sellers](https://docs.proofage.net/recipes/marketplace-sellers.md): the same flow built with the API. * Sharetribe Help Center: [Zapier integration introduction](https://www.sharetribe.com/help/en/articles/8529941-zapier-integration-introduction) and [How the Sharetribe-Zapier integration works](https://www.sharetribe.com/help/en/articles/8529989-how-the-sharetribe-zapier-integration-works). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.