Skip to main content
Every call is server-to-server with your partner key. Substitute your own merchant id for merchant_8812 — that id is the only handle you ever use.
All examples use https://api.impellabs.tech/api/v1. Set $KEY to your tgpk_… secret.

1. Provision the tenant

201 on create, 200 on a repeat. Safe to retry after a timeout — see idempotency. No email is sent and the merchant cannot log in; they were never asked to. monthly_credit_cap is required. It is the brake between one busy merchant and your invoice.

2. Give it knowledge

Send everything you have, every time. Anything you stop sending is removed, and re-sending unchanged text costs nothing. You never track our ids.

3. Connect your tools

The same URL for every merchant, a different token each time. Your server resolves which merchant from the token. See tool servers.

4. Create the assistant

tool_servers must be enabled or the tools from step 3 are ignored.

5. Set up the website channel

Paste embed_snippet into the merchant’s storefront. allowed_origins is required — an unrestricted key is one anyone can lift off the page.

6. Go live

Until this call the widget answers 503. Provisioned and live are separate states on purpose: an assistant that starts talking to customers the moment it exists is the worst possible first impression. If you want your merchant to preview first, this is where that screen goes.

What to build next

Tool server

The half that lives in your codebase.

Usage and caps

Watch spend before the invoice, not after.