Accept Seller Lead in VTEX Marketplace
A documented VTEX Marketplace operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Accept Seller Lead
- PUTChanges data · Seller Invite
vtex.local/seller-register/pvt/seller-leads/{sellerLeadId}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which VTEX Marketplace operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other VTEX Marketplace operations
- Invite Seller LeadPOST · changes data
- Create Seller From LeadPUT · changes data
- Delete Seller LeadDELETE · changes data
- Resend Seller Lead InvitePUT · changes data
- Notify marketplace of price updatePOST · changes data
- Notify marketplace of inventory updatePOST · changes data
- Configure Seller AccountPOST · changes data
- Update Seller by Seller IDPATCH · changes data
Questions
- Can HumDay accept seller lead in VTEX Marketplace?
- Yes. This operation is published in VTEX Marketplace's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my VTEX Marketplace data?
- Yes — this is a PUT operation, so it changes something in VTEX Marketplace. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your VTEX Marketplace account.
Where this came from
Read from a published API description for VTEX Marketplace at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Marketplace APIs.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.