Integrations and the API

Seven entries under Setups connect SaleSprint to the outside world. They are not all at the same stage.

Menu entry	State
API Keys	works
Webhooks	works
E-Invoice Providers	works — Ghana GRA
Fiscal Transmissions	works
Accounting Providers	stores settings, no sync engine
Accounting Sync Jobs	queues jobs that never run
External Mappings	stores pairs nothing reads

Tax transmission (Ghana GRA)

Where

Setups → E-Invoice Providers

Plan

Professional and above

Permission

Integration → Einvoice Provider

This is the real, working connection to the Ghana Revenue Authority’s E-VAT system. Invoices are transmitted and the fiscal signature comes back onto your receipts.

How to set it up

1. Go to Setups → E-Invoice Providers and click to add one.
2. Type a Name, and set Provider to exactly gra.
3. Enter your Taxpayer ID — your company TIN.
4. Put your GRA security key in Client secret, and your registered company name in External realm ID.
5. Choose the Environment. Production requires a Base URL override — the live address GRA issues you at onboarding. Sandbox does not.
6. Turn on Transmission enabled and save.
7. Use Test connection on the row to check it before you rely on it.

The Provider hint is wrong on this screen

It suggests “e.g. quickbooks, xero”. On this screen the only valid values are gra and stub.

Nothing transmits until you switch on e-invoicing in settings

A provider that is configured, shows Connected and passes Test connection will still send nothing. Transmission is controlled by a separate setting that is off by default and is not on this screen — it lives in your workspace settings.

Turn on e-invoicing there, and set which document types to transmit. Nothing on the provider screen mentions this.

Watching what was sent

Fiscal Transmissions is the log: the document, its status, how many attempts, and the fiscal reference. Fiscal details on a row shows the full signature sheet — SDC ID, receipt number, device code and the verification QR link.

Failed transmissions retry automatically, backing off from 30 seconds to a day, up to twelve attempts. A document already lodged is never sent twice; only its signature is re-fetched.

Two buttons that look alike — only one transmits

Transmit is the one that actually sends a document to GRA. Use this.

Submit document only records a transmission in the log. It reports “Transmission submitted” and sends nothing at all. Ignore it.

The public API

Where

Setups → API Keys

Plan

Professional and above

Permission

Integration → Api Key

These two menu entries never appear, for anybody

API Keys and Webhooks are shown only to someone holding a permission that does not exist — the menu asks for integration, which is a category name rather than a real permission, so it can never be granted.

In a normal business both entries are invisible. The screens can still be reached by typing /api-keys or /webhooks into the address bar — but then the New, Edit, Revoke and Delete buttons do not appear either, for the same reason.

In practice, only a SaleSprint operator can use these today.

With that said, the feature behind them is real.

What the API can do

Eight operations, at /public/v1: list and fetch products, orders, customers and inventory, plus creating a customer — the only write.

A key carries scopes, but catalog:write and orders:write unlock nothing, because no such operations exist. Only customers:write does anything.

A key can never do more than the person who created it could.

How to create a key

1. Go to Setups → API Keys and create one.
2. Give it a Name.
3. Tick the Scopes it needs.
4. Optionally set Expires at.
5. Save, then copy the key immediately — the dialog says “Copy your API key now”, and it is genuinely the only time it is shown.

The expiry date needs a time on it

The hint says YYYY-MM-DD, but typing 2026-12-31 is rejected. Write 2026-12-31T00:00:00Z.

Revoking a key takes effect immediately.

Webhooks

A webhook posts to your address when something changes.

1. Give it a Name and an Endpoint URL.
2. Leave Event types blank to receive everything, or list them comma-separated.
3. Set a Signing secret so you can verify the messages are really from SaleSprint.
4. Leave Active on.

There are only five events, and they are generic

record.created, record.updated, record.deleted, record.cancelled and the catch-all record.changed. A sale being created and a product being edited both arrive as the same event — your system has to look at the type inside the message to tell them apart.

The message carries what changed, not the record itself. You then fetch the record through the API.

The Event types box is free text with no list, so a typo silently receives nothing.

Failed deliveries retry eight times, backing off from 30 seconds to six hours.

There is no delivery log you can see

SaleSprint records whether each delivery succeeded, but nothing displays it. You cannot tell from inside the app whether your endpoint ever received anything.

Accounting — groundwork only

Where

Setups → Accounting Providers

Plan

Professional and above

Permission

Integration → Accounting Provider

There is no accounting sync. Nothing is sent anywhere.

You can add an accounting provider, fill in credentials and press Connect. The row will then say Connected — but nothing was contacted and nothing was verified. It only wrote the word.

Accounting Sync Jobs lets you queue a document for syncing. The job is created and stays Pending for ever. There is no engine to run it, no scheduled task, and posting a sale never queues anything. The “Update sync job status” action exists only so a person can type in an outcome by hand.

External Mappings stores “our record = their record” pairs. Nothing reads them. Both identifier boxes ask you to hand-type raw internal references with no lookup.

None of these three does anything today. Do not build a bookkeeping routine around them.

If you need your figures in an accounting package, export the financial reports and import them there.

Who can use these

All seven need their own permission. Accounting Providers, Sync Jobs, External Mappings, E-Invoice Providers and Fiscal Transmissions are permission-gated only and will work on any plan if the permission is granted.

API Keys and Webhooks additionally need a plan that includes API access — roughly Growth to view and Professional to create — and are subject to the visibility problem described above.

Related

• Financial reports
• Tax
• Settings — where e-invoicing is switched on