Explain how to finish connecting this bridge to Growwer. The bridge has no API key, so no project, order, wallet or seller data can be read until one is configured.

Use this when a seller takes an order placed on one of their medias that waits for acceptance: accepts it and the buyer is told.

Use this when a seller wants the fees Growwer suggests for one of their medias: sets its post fees to the competitiveFees growwer_get_seller_media answers.

Use this when the user has checked the delivery of an order that waits for their review and accepts it: the order finishes and the seller is paid. It cannot be undone. The user is asked to confirm first.

Use this when the user has read the draft of a post order that waits for their review and accepts it: the seller then publishes it.

Use this when the user wants to cancel an order the seller has not accepted yet: cancels it, its price returns to their wallet and the seller is told the reason. The user is asked to confirm first.

Use this when you need how many catalogue medias one saved filter of a project matches, without listing them: the total growwer_search_project_medias answers with that savedFilterId.

Use this when the user has decided to buy an article or a link addition on a catalogue media for one of their projects: places the order, and its price leaves their wallet. Send the price growwer_estimate_order answered as expectedPrice. The user is asked to confirm the purchase first, and nothing is charged unless they accept.

Use this when the user wants to buy links for a website that has no project yet: creates the project, which Growwer then analyses in the background to recommend medias.

Use this when the user wants to keep a catalogue search of a project to reuse it, here or on the web: saves the filters growwer_search_project_medias takes, optionally with notifications of new matching medias.

Use this when a seller wants to offer a new website of theirs on Growwer: registers the media with its fees and offer, and Growwer reviews it in the background.

Use this when the user no longer wants one of their projects: deletes it for good. A project with an order in progress cannot be deleted. The user is asked to confirm first.

Use this when the user no longer wants one of the saved filters of a project, including one saved on the web: deletes it and stops its notifications.

Use this when a seller wants to stop offering one of their medias for good: deletes it, as the web's delete button does. A media with an order in progress cannot be deleted. The user is asked to confirm first.

Use this when a seller has published an accepted order: delivers a post order with the URL of the post and publicationDateConfirmed, and a link addition with neither, for the buyer to review.

Use this when a seller who writes the draft of a post order has it ready: delivers it from a file uploaded with growwer_upload_file.

Use this when a seller has changed the draft of a post order as the buyer asked: delivers the new draft from a file uploaded with growwer_upload_file.

Use this when a seller has changed a delivered order as the buyer asked: delivers a post order with the URL of the post and publicationDateConfirmed, and a link addition with neither, for the buyer to review again.

Use this when the user does not want a catalogue media for one of their projects: discards it for that project, as the web does. Discarding it again changes nothing.

Use this when the user needs the document Growwer attached to a movement of their buyer wallet: returns the file. Find the movement with growwer_list_buyer_transactions.

Use this when the user needs the file they attached to the briefing of one of their post orders: returns the file.

Use this when the user needs the current draft file of one of their post orders, to review it before publishing: returns the file.

Use this when the user, as a seller, needs the file the buyer attached to the briefing of a post order they sell: returns the file.

Use this when the user, as a seller, needs the current draft file of a post order they sell: returns the file.

Use this when the user needs the document Growwer attached to a movement of their seller wallet: returns the file. Find the movement with growwer_list_seller_transactions.

Use this when the user needs the invoice they uploaded for one of their withdrawals: returns the file.

Use this when the user considers accepting proposals of a managed service campaign: totals the accepted proposals still awaiting their order and the proposed ones named in accept, and compares the total with the available wallet balance. Changes nothing.

Use this when the user considers buying an article on a media: checks and prices the order these arguments describe and compares the price with the available wallet balance. Changes nothing.

Use this when the user likes a catalogue media for one of their projects: marks it as a favourite of that project, as the heart on the web does. Adding it again changes nothing.

Use this when the user asks how much they can spend: answers the balance of their buyer wallet and the page where they top it up.

Use this when you need the full details of one media of the catalogue, such as its prices, metrics and conditions, before estimating or recommending an order on it.

Use this when you start working with Growwer, or when a tool answer is unclear: explains the buyer and seller profiles, the order states, paging, the error codes and where the vocabulary ids come from. Needs no sign-in or API key.

Use this when the user needs the PDF of one of their top-up invoices: returns the file. Find the invoice id with growwer_list_invoices.

Use this when you need one managed service campaign in full: its budget, targets, state and progress.

Use this when the user wants the PDF summary of a managed service campaign's proposals, as the campaign page offers it; extended adds the details of each media. Returns the file.

Use this when you start working with an account, or need its profiles, balances or access: answers the profile basics, the buyer and seller balances, whether the seller account is restricted, whether the catalogue is open to it, and whether it has a managed service.

Use this when you need one order the user bought in full: its briefing, its draft and its state history.

Use this when you need one of the user's projects in full, such as its domain, its topics and its state.

Use this when you need one of the user's seller medias in full: its fees, extras, the competitive fees Growwer suggests and its performance.

Use this when you need one order placed on one of the user's medias in full: its briefing, its draft and its state history.

Use this when the user asks what their sales earned: answers the balance they can withdraw now and what is held until orders settle.

Use this when a filter or an answer takes a country, language, topic, product type or link type: lists every code with its English name, so the ids are never guessed.

Use this when the user asks about the movements of their buyer wallet: lists top-ups, order debits and their refunds, gifts and manual corrections, newest first.

Use this when the user looks for discounted medias: lists the medias on a time-limited flash offer in the catalogue of one of their projects.

Use this when the user asks about the invoices of their top-ups: lists them, newest first, with their amounts and dates.

Use this when the user asks about the campaigns Growwer's team runs for them: lists their managed service campaigns, newest first. Empty without a managed service.

Use this when the user reviews what Growwer's team proposes for a managed service campaign: lists the proposed medias, newest first, with their state and price.

Use this when the user asks about the orders they bought, or to follow them: lists them with filters on state, project and dates; sort by updatedAt with updatedSince to see only what changed.

Use this when you need the user's projects (the websites they buy for), for example to pick the project id the catalogue and order tools take: lists them, newest first.

Use this when the user refers to a catalogue search they saved, on the web or here: lists the saved filters of one project, newest first, to apply one with savedFilterId in growwer_search_project_medias.

Use this when the user asks about the medias they sell articles on: lists them in every state with their fees and performance.

Use this when the user, as a seller, asks about the orders placed on their medias, or to follow them: lists them with filters; sort by updatedAt with updatedSince to see only what changed.

Use this when the user asks about the movements of their seller wallet: lists earnings from orders, withdrawals and manual corrections, newest first.

Use this when the user asks about the withdrawals they requested from their seller wallet: lists them, newest first, with their state.

Use this when a seller wants to start, change or end their holiday: while on holiday their medias take no orders. Setting the holiday they already have changes nothing.

Use this when a seller will not change a draft as the buyer asked: refuses the update with a reason the buyer is told.

Use this when a seller will not change a delivered order as the buyer asked: refuses the update with a reason the buyer is told.

Use this when a seller will not take an order placed on one of their medias that waits for acceptance: rejects it, the buyer gets the price back and is told the reason. The user is asked to confirm first.

Use this when a user with a managed service wants Growwer's team to run a new campaign: asks their account manager for it, and the team emails them to agree on it.

Use this when a user without a managed service wants Growwer's team to run their link building: asks the team about it for their website, and the team contacts them.

Use this when the user wants medias on particular domains the catalogue does not offer for a project: asks Growwer to find them, as the web's "request specific domains" form does.

Use this when the user wants the seller to change the draft of a post order that waits for their review: sends the seller the reason.

Use this when the user wants the seller to change the delivery of an order that waits for their review: sends the seller the reason.

Use this when the user has decided on every proposal of a managed service campaign that awaits their review: accepts or rejects each one; the team then places the orders of the accepted ones, which their wallet pays. growwer_estimate_managed_service_proposals says what they cost. The user is asked to confirm first.

Use this when the user wants media to publish on for one of their projects: searches the catalogue with filters on price, metrics, topics, languages, countries and more, and answers each media with its state in the project.

Use this when the user wants back a media they discarded for one of their projects: removes the discard. Restoring one that is not discarded changes nothing.

Use this when the user no longer wants a media among the favourites of one of their projects: removes it. Removing one that is not a favourite changes nothing.

Use this when the user wants to change the settings of one of their projects, such as its name, language, country, topics or promoted products: changes only the fields sent.

Use this when a seller wants to change the fees, extra services, typology or post offer of one of their medias: replaces each field sent and keeps the rest.

Use this when a later write needs a document, such as a seller delivering a draft: uploads an odt, doc, docx or txt file of at most 3 MB, sent as its name and base64 content, and answers its id for that write. The file expires after 24 hours.