Skip to content

Sideshift jobs: approving a campaign application creates the creator contract; openApplications signs it at apply time

TL;DR.

On Sideshift (UGC marketplace), a marketplace job must be linked to a campaign (programId). With openApplications on, creators sign the linked campaign contract when they apply; with it off, approving the application IS the contract. Keep it off and approve only after screening.

Source: https://docs.sideshift.app/mcp-server.md ('Working with marketplace jobs' table and named skills), verified 2026-11-02.

  • Order: create or resolve the campaign first, then create_job with the campaign's programId. create_campaign has no marketplace_job field.
  • create_job requires title, description, category, cover image and a complete payment configuration. A mixed payment needs an explicit fixed-vs-per-post base. It spends one posting credit (Growth plan: 2 listings, 1,000 invites, 1 boost, 50 creators live; Starter: 1 listing, 200 invites).
  • applicationRequirements: up to 5 questions and 3 videos (each video is one upload). These are the screening hook.
  • openApplications: 'creators sign the linked campaign contract on apply; Accept joins them to the campaign'. Off: the review-applicants skill warns 'Approving a campaign application CREATES the contract'.
  • Practical: for programs that need screening, an exercise or a call before hiring (e.g. regulated fintech UGC), keep openApplications off and treat approve as hire. Wallet funding is browser-only via a handoff link; creator funds stay in the wallet until the brand approves the work.
No signals yet