Businesslogic API documentation

Here is an explanation how you can call Excel Microservices from your programming environment using curl.

Execute endpoint

/execute is used to execute provided input parameters in the uploaded Excel document to retrieve the calculated output.

      
curl -i -X POST https://api.businesslogic.online/execute  \
  -H "X-Auth-Token:5009a8b8529d4c059560a863f8904e31"  \
  -H "Content-Type: application/json"  \
  -d '{
  "salary_per_month": null,
  "start_year": null
}'

Describe endpoint

/describe returns json schemas for input and output parameters.

      
curl -i -X GET https://api.businesslogic.online/describe  \
  -H "X-Auth-Token:5009a8b8529d4c059560a863f8904e31"

Json schema for input parameters describes what your webservice expects to receive as input parameters. It can be use to build and validate online forms automatically using json schema forms. Json schema describes which parameters you can expect from output and can be used to build UI to represent the output automatically.

How the API fits together

Every Businesslogic web service exposes two endpoints. Call /execute with your input values to run the underlying Excel model and receive the calculated outputs as JSON. Call /describe to retrieve the input and output schema — useful for building forms, validating requests, or letting another system discover how to talk to your service automatically.

Requests and responses are plain JSON, and each call is authenticated with your service token sent in the X-Auth-Token header, so you can integrate from any programming language or no-code automation tool. Because the endpoint runs on your real spreadsheet, updating the Excel file and re-publishing is all it takes to change the logic — the API contract stays the same.

New to this? Start with the guide on turning an Excel spreadsheet into a REST API, or see the Formula module and Workbook module for using Excel inside Make (Integromat) scenarios.

Common integration patterns

Most teams use a Businesslogic endpoint in one of a few ways:

  • Live calculator on your site. A form posts the user's inputs to /execute and shows the returned figure — a price, a quote, a score — without exposing the model behind it.
  • Step inside an automation. Call the service from Make, Zapier or n8n so a spreadsheet calculation runs as one node in a larger workflow, then pass the result downstream.
  • Server-to-server lookup. Your backend calls the API to apply a pricing rule, eligibility check or engineering formula, keeping one source of truth instead of re-implementing the logic in code.
  • Self-describing client. Read /describe first to generate inputs and validation automatically, so the client adapts when the Excel model changes.

Keep your X-Auth-Token on the server side — never embed it in browser code or a public repository.