Developers / API

Connect your shop to the rest of your software

The Promec REST API lets your accountant, your ERP, a customer's fleet manager or your own website read and write shop data without spreadsheets going back and forth. The shop's management switches it on, with scopes per area and a log of every request.

  • 56endpoints in v1
  • 42webhook events
  • 60requests per minute per key
  • GDPR: a stated purpose on every key
  • Each key bound to one shop
  • HMAC-SHA256 signed webhooks
  • 90-day request log
  • Idempotency-Key on writes
  • Invoicing with the app's own numbering and tax reporting

What shops use it for

Integrations people actually ask us for. If yours isn't here, tell us about it — it usually fits the endpoints that already exist.

Accountant and bookkeeping

Your accountant pulls the month's issued invoices, PDFs and payments directly, instead of chasing you by email. Your system can also invoice an approved quote and record the payment: the invoice goes out with the program's own numbering and tax-authority reporting.

Group or dealer ERP

If the shop belongs to a group, keep clients, vehicles and quotes in sync with the central system and get notified the moment an invoice is issued.

Fleets and leasing

The fleet manager checks where each vehicle is in the process and when its inspection is due, and gets a webhook when it arrives, when it's ready and when it's handed back.

Parts suppliers

A distributor can open quotes with the part numbers already on each line, or read a job's lines to prepare the order.

Your website or app

Your site reads the free slots in the real diary and proposes the appointment. You confirm it in one click — or, in direct-booking mode, it goes straight in.

Make, n8n or Zapier

Receive events by webhook and chain whatever you need: a task in your CRM when a quote is rejected, a row in a sheet every time a payment comes in. And if you have your own bot or AI, it can answer the shop's WhatsApp, SMS, chat and email messages.

How it works

From your first key to a live integration without setting up a single server. The API is already part of your Promec.

  1. Create a test keyIn Developers / API, the shop's management creates the key with a name, the purpose of the integration and scopes per area. The full key is shown only once.
  2. Call /pingUsing your shop's URL (https://<your-domain>/api/v1). It returns the key's scopes and how much of today's quota is left.
  3. Build against real datapt_test_ keys on your shop read its data but can't create, change or send anything, and they don't use quota. To try writes, acceptances, invoices and messages too, use the public test environment.
  4. Go live and subscribe to webhooksOnce everything checks out, create a pt_live_ key and register the URL that will receive events. Every change is signed as “API · key name”.
See every endpoint →

Available resources

What an integration can read and write in version 1. Each resource has its own scope, so every key only sees what it needs.

Clients

Search by name, phone or email, and create or edit client records with their contact details.

  • GET/clients
  • POST/clients
  • GET/clients/{id}
  • PATCH/clients/{id}
See in the reference →

Vehicles

Look up by plate or by client, create and edit, with mileage and inspection due date.

  • GET/vehicles
  • POST/vehicles
  • GET/vehicles/{id}
  • PATCH/vehicles/{id}
  • +1 more
See in the reference →

Quotes

Create quotes with their lines, move them through statuses and attach photos or PDFs. Accept or reject them on the customer's behalf, with evidence of who and through which channel.

  • GET/budgets
  • POST/budgets
  • GET/budgets/{id}
  • GET/budgets/{id}/activity
  • +7 more
See in the reference →

Invoices and PDF

Issued invoices with lines, totals per tax rate, payments and the original PDF. Invoice an approved quote and record payments, with the program's own numbering and tax reporting.

  • POST/budgets/{id}/invoice
  • GET/invoices
  • GET/invoices/{id}
  • GET/invoices/{id}/pdf
  • +1 more
See in the reference →

Appointments

Free slots using the diary's own rules (opening hours, bays, holidays), plus proposals and confirmed bookings.

  • GET/appointments
  • POST/appointments
  • GET/appointments/availability
  • DELETE/appointments/{id}
  • +2 more
See in the reference →

Catalog

The shop's services and rates, so your website or configurator shows the same prices.

  • GET/catalog/services
  • GET/catalog/rates
See in the reference →

Parts stock

Stock levels, references and selling price from the inventory. Cost and supplier never leave through the API.

  • GET/stock
  • GET/stock/{id}
See in the reference →

Communications

Log of emails, texts, WhatsApp messages and calls. On Business, send email and SMS too.

  • GET/communications
  • GET/logs
  • POST/email
  • POST/sms
See in the reference →

Conversations

WhatsApp, SMS, web chat and email in one list, like the program's Inbox: read the thread and reply as the shop.

  • GET/conversations
  • GET/conversations/{key}/messages
  • POST/conversations/{key}/messages
  • GET/messages/templates
See in the reference →

External assistant

Choose the channels where your bot or AI answers instead of the program's assistant, with automatic fallback if it doesn't reply within 10 minutes.

  • GET/settings/assistant
  • PUT/settings/assistant
See in the reference →

Webhooks

Per-event subscriptions with HMAC-SHA256 signatures, retries and an on-demand test delivery.

Some events

lead.acceptedvehicle.readyinvoice.issuedpayment.receivedappointment.proposed+37 more
See in the reference →

Test environment

A public instance with fictitious data to try writes, acceptances, invoices and messages safely, with 30-day pt_test_ keys.

  • POST/sandbox/keys
  • POST/sandbox/simulate/message
See in the reference →

Built for integrations that don't break

The details that usually cause trouble in an integration, handled out of the box.

Keys created by management

The shop owner or manager creates each key with a name, a stated purpose and its scopes. The full key is shown once; after that only its prefix is visible.

Scopes per area

Clients, vehicles, quotes, invoices, appointments, catalog and communications, with read and, where it makes sense, write access. Your accountant's key has no business seeing the diary.

Test and live

pt_test_ keys on your shop read real data but can't create or change anything, and they don't use quota. To try writes, acceptances, invoices and messages there's a public test environment with fictitious data. Once the integration works, you create a pt_live_ key.

Signed webhooks

Promec calls your URL when something happens: more than 40 events, from “quote accepted” to “vehicle ready”. Every delivery is signed with HMAC-SHA256 and retried up to 5 times if your server doesn't answer.

Visible limits

60 requests per minute per key (up to 600 on request) plus your plan's daily quota. Every response carries X-RateLimit-Remaining; go over and you get a 429 with Retry-After.

No duplicate writes

Every POST carries an Idempotency-Key: if your system retries after a network drop, you won't end up with a second client or a second quote.

Security and GDPR

An integration shouldn't open more doors than it needs. This is how it's built:

One key, one shop

Only a hash of the key is stored, bound to the shop's instance: it's useless anywhere else and nobody can recover it, us included.

Purpose is mandatory

When creating a key you have to state what the data will be used for, as GDPR requires. It stays next to the key and in the log.

Internal data stays internal

Costs, margins, internal notes and internal-use quotes never appear in a response. Shop staff only show up as an id and a name.

Every request logged

Which key, from which IP, to which endpoint and with what result. Kept for 90 days and visible in the same section.

IP allow lists and expiry

Restrict a key to the IPs of the provider using it and give it an end date. Revoking it takes effect immediately.

Acceptance leaves a trail

Accepting or rejecting a quote through the API needs a separate scope (budgets:accept) and evidence of who accepted and through which channel. It is recorded in the history as “Accepted by API on the customer's behalf”, with the key's name.

API plans

Separate from your Promec plan. Start on Included and only move up if you need to write data, receive webhooks or handle more volume.

Included
Comes with any Promec plan.
0€/mo
excl. taxes
See Promec plans
  • 1 live key
  • Read-only, every area
  • 2,000 requests a day
  • Pauses at the quota until 00:00 UTC
Your own integrations
Developer
For connecting your own tools, accepting quotes and invoicing.
19€/mo
excl. taxes
Talk to sales
  • 5 live keys
  • Read and write
  • Webhooks
  • Accept quotes and invoice
  • 20,000 requests a day
Business
When the integration sends messages or runs your channels with your own assistant.
49€/mo
excl. taxes
Talk to sales
  • Unlimited keys
  • Everything in Developer
  • Messages via the API (email, SMS, WhatsApp and chat) and an external assistant on your channels (messages billed separately)
  • 100,000 requests a day
  • Email support
Partner
For software that serves many shops.
from5€/shop/mo
excl. taxes
Ask about Partner
  • For companies connecting their product to several shops
  • Custom quota, keys and scopes
  • Volume pricing

Prices exclude taxes. Test keys are free and never count towards quota, and neither do tests run from the panel. If Developer or Business go over their monthly allowance (daily quota × days in the month), the excess is billed at €1 per 1,000 requests.

Frequently asked questions

Do I have to pay to use the API?

No. The Included plan comes with any Promec plan: one read-only key and 2,000 requests a day. You only pay if you need to write data, use webhooks or need more volume.

Where do I find my shop's API URL?

In the Developers / API section of Promec. Every shop runs on its own domain, so the base URL looks like https://<your-domain>/api/v1.

Can I issue invoices through the API?

Yes, with a separate scope (invoices:write), from the Developer plan. The API uses the program's own invoicing: series, sequential numbering, tax-authority registration and the accounting entry. You invoice an approved quote (a standalone invoice can't be created), and credit notes are made from the program.

What if the integration gets something wrong?

A test key can't change anything. With a live key, every change is recorded in the client's or quote's history as “API · key name”, and you can revoke the key instantly.

Is there an SDK or a Postman collection?

The OpenAPI 3.1 file lets you generate a client in any language. Inside Promec you'll also find a Postman collection and a panel to try every endpoint with your own key.

I build software for repair shops — can I connect to many of them?

Yes, on the Partner plan: each shop creates a key for your product and we agree a per-shop price based on volume. Get in touch and we'll work it out.

What happens if I hit the rate limit?

Each key allows 60 requests per minute. Go over and the API answers 429 with a Retry-After header, so your system just waits that many seconds. On Included, the daily quota pauses the key until 00:00 UTC; on Developer and Business requests keep going through and the excess is billed at €1 per 1,000.

Can the API accept a quote on the customer's behalf?

Yes, with the budgets:accept scope (Developer plan or higher) and only if you supply the evidence: who accepted and through which channel (phone, in person, email, WhatsApp…). It goes through the program's own acceptance rules and the history shows “Accepted by API on the customer's behalf” with the key's name. Customers can still accept from their tracking link; the API never hands out that link.

Is there a test environment?

Yes, public and free: https://demo.programa-taller.es/desarrolladores-sandbox. It gives you a 30-day pt_test_ key with write access on fictitious data that is restored every 2 hours. Nothing is really sent (messages are logged as simulated) and webhooks still fire, so you can test the whole cycle. Your keys and webhooks survive the resets.

Can my own bot reply to the shop's customers?

Yes, from the Business plan. You switch on the “external assistant” for the channels you want (WhatsApp, SMS, web chat or email): each customer message reaches you through the message.received webhook and you reply through the API. If you don't reply within 10 minutes, or your key or webhook stops working, the program's assistant answers for you.

Got an integration in mind?

Tell us what you want to connect and we'll point you to the right endpoints and the plan that fits.

3 months for €1