Does Bsale have a public API?
Yes. Bsale documents its REST API for Chile, Peru and Mexico, with a test account to build in. The production token is requested from Bsale or obtained through OAuth 2.0.
The most direct route is Bsale's REST API, which is documented and sends webhooks when a document is issued or stock changes; you can also use a middleware or a file exchange. Typically, the deal won in HubSpot creates the sales note or the document in Bsale, and the invoice comes back with its number and its PDF. Before committing, check your API access, its limits and which documents you issue in Chile, Peru or Mexico.
Client with tax ID, products with their variant code and payment terms.
The API creates the sales note or the electronic document and declares it to the SII if told to.
Bsale notifies an integration URL every time a document is issued.
Number, amount, PDF and status on the deal and the company.
Bsale publishes a documented REST API for Chile, Peru and Mexico. Every call carries an access token in the header; you can build in a test account, and the production token is requested from Bsale or obtained through OAuth 2.0 if you register your integration. Responses are paginated, with up to 50 records per page.
It covers what a sales integration needs: clients, whose code is the tax ID; products and variants with their code; available and reserved stock; price lists; document types with their SII code; and sales documents, including electronic invoices and receipts, sales notes and quotes.
Products, prices and stock travel from Bsale, so HubSpot quotes use the same variant code. The client is born in HubSpot and is looked up by tax ID in Bsale before being created. The won deal creates the sales note or the document in Bsale, depending on your process.
On the way back, the issued document updates the deal and the company with number, amount, PDF link and status. Bsale owns what was invoiced and the stock; HubSpot owns the pipeline. Each number is reconciled against its own records.
When creating a document through the API, a field says whether it is declared to the SII, and Bsale responds with the assigned number and links to the PDF and the XML. Check the document types you have enabled and the available number ranges first: the API lets you query them.
Typical errors are data errors: tax IDs in a different format, products without a variant code, prices with and without taxes mixed up or the wrong document type. Validate those fields in HubSpot before the deal is won and test in the test account with real documents from your operation.
Bsale webhooks notify when a document is created or when stock, a product, a variant or a price changes, and they are activated by writing to Bsale with the destination URL. There is no client webhook, so those changes are polled periodically. The API accepts up to 8 calls per second: large loads must respect that pace.
In HubSpot, the Record Source property shows what the integration created, and a daily report by source tells you whether documents keep arriving. Add a silence alert: if no document arrives on a business day with sales, someone gets the notice. In Chile and Latin America, a webhook that stops responding can go days without anyone seeing it.
Six steps before committing to dates.
A test account to build in and the production token requested from Bsale or through OAuth 2.0, in your company's name.
Client, product, variant, price, stock, deal and document: a table with the owner of each piece of data and when it travels.
On the company, the tax ID as a unique property; on the product, the variant code; on the deal, document type, number, amount and PDF link.
A sales note, a quote or an electronic document, and whether it is declared to the SII right away or after a review.
Turn on the document, stock and price webhooks to an integration URL, and test with real sales in the test account.
Code and token in your company's name, a document of what syncs and an alert if documents stop arriving.

Products without a variant code in HubSpot, which force fixes on every document.
Mixing prices with and without taxes between the quote and the invoice.
Bulk loads that exceed the calls-per-second limit and stop halfway.
Active webhooks without monitoring: they stop arriving and nobody notices.
30 minutes with Roberto. No demo and no access to your CRM.
We review your Bsale API access, the documents you issue and your sales volume, and classify each point as confirmed, conditional or unsupported before quoting. If we move forward, it is at a fixed price, and we hand over code, token and manual in your name, with the silence alert active.
ERP, invoicing, WhatsApp and APIs, with code and manual in your name and an alert if they stop bringing data.
See IntegrationsIn 10 hours we inventory integrations, workflows and properties, with the risk list.
See the DiagnosticThe alert is reviewed weekly in Managed HubSpot and daily in Dedicated HubSpot.
See operations plansThe guarantees that apply
An automatic alert tells you if an integration or form stops bringing in data. You hear it from us first.
Workflows, integrations, code and keys documented and in your name. If you change partners, you lose nothing.
We put them in writing because they are what we control.
Yes. Bsale documents its REST API for Chile, Peru and Mexico, with a test account to build in. The production token is requested from Bsale or obtained through OAuth 2.0.
The integration can create the document in Bsale when the deal is won, and Bsale declares it to the SII if told to. HubSpot does not issue the tax document: it receives the number, the amount and the PDF.
Yes, with webhooks for documents, stock, products, variants and prices, among others. There is no client webhook. They are activated by writing to Bsale with the destination URL.
Up to 8 calls per second and up to 50 records per page. A large initial load must be done in batches and at that pace.
It depends on the objects, the volume of documents and whether you need stock and prices in HubSpot; that is why it should be evaluated before quoting. Ask for a fixed price, code in your name and an alert if the integration stops bringing data.

We review one concrete problem, its impact and your starting point. No demo and no access to your CRM.