Skip to main content
Most blocked actions on DataVendor come from one of four rules: the action needs a team admin, a vendor tier, a live listing, or supply DataVendor accepts. Find the symptom below.

​
Account and access

Moving money and making deals needs a team admin: buying, bidding, invoicing, accepting or rejecting bids, converting earnings, and withdrawing. Ask an admin to do it, or to make you an admin under Settings → Members. See Members and admins.
Vendor-only teams are behind the browse gate until they have 2 live published listings. Hiding or archiving listings can lock it again. Buyer teams are exempt.
Opportunities need Tier 2. Choose Request tier 2 and sign the Platform Access Agreement; Tier 2 is granted as soon as you sign. See Vendor tiers.
Buyer access is invite-only, and DataVendor approves organizations from the waitlist at a managed pace. You can keep using other organizations meanwhile. See Become a buyer.
A referral counts only the first time an organization gets vendor access, and only when you sign up through the referral link. An organization that already sells cannot be credited.
The key’s team has no marketplace role, the Mutual NDA has not been accepted, or a vendor-only team hit the browse gate with a search, filter, or cursor. See Using the API.

​
Selling

Public repositories are hidden in Inventory and disabled in listing pickers, because buyers can already clone them. For a private repository, check that the account you connected can read it: on GitHub, choose Manage in GitHub in Connectors and grant the app access to it.
DataVendor could not save a copy of the repository, usually because the connection lost access. Choose Reconnect for that account in Connectors; the copy retries.
DataVendor no longer accepts new supply of that kind, such as Harbor tasks or standalone environments. Existing assets and listings that carry them keep working. See What you can sell.
Codebases and Raw data with linked data can be listed from Inventory; other kinds cannot yet. List HUD tasksets from Listings, and link data to proposed codebases first.
Open the listing and look at Quality checks. If Required to publish shows Blocked, a mandatory check failed: read the reason under the issue, edit the listing, and submit it again. A check marked On our side could not finish on DataVendor’s side; choose Run checks again. If only Verified badge has issues, fix them and resubmit, or choose Skip review to reach Ready without the badge. See Quality checks.
A listing that anyone has bought or sampled cannot be hidden, because buyers hold access to it. Archive it instead with Archive listing. See Take a listing down.
Only listings with HUD tasksets that hold at least two runnable tasks can offer a sample, and only once you set a Sample price.
Withdrawals need settled earnings (14 days after payment), at least $1,000 available, finished Stripe payout setup, a team admin, and no other withdrawal in progress. See Get paid.

​
Buying

Listings and accepted bids over $5,000 pay by invoice. See Pay by invoice.
An unpaid invoice blocks further purchases of that listing. Pay it, or choose Cancel invoice under Purchases.
Your team can hold one open bid per listing. Wait for the vendor’s decision; once a bid is rejected, you can bid again.
Choose Copy environments to your team again on the purchase; DataVendor restores the copy.

​
Still have questions?

Book a call with the DataVendor team to talk through your supply, buyer needs, or marketplace fit. Signed-in teams can also send feedback from the app sidebar.