The Wiring Lab

The Wiring Lab is where you connect a persona to an engine. That connection is called a link: it pairs exactly one persona with one engine, so the engine runs in that persona's voice. Each link gets its own api_slug, a unique identifier for that specific wiring, so the platform always knows which persona-and-engine combination a request belongs to.

To wire a link:

Open the Wiring Lab and pick the persona you want to bring online.
Drag an engine from the library onto the canvas to attach it to that persona.
Hit Save (the Commit Wiringbutton) to persist the link. Until you commit, the wiring isn't saved.

You can wire several persona-engine links in one account. Each is its own connection with its own api_slug.

API keys

An API key is how an outside bot or integration authenticates to FluidTalk. There are two ways to make one:

Create: generate a plain, account-wide key that isn't tied to any persona or engine yet.
Provision: generate a key that is scoped to a specific persona and engine in one step. This is the recommended path, because a key that is already scoped is ready to serve live traffic.

You manage keys from the Wiring Lab:

Link / scope a key: bind an existing account-wide key to a persona and engine (and optionally rename it). A key that is never scoped can't serve live calls.
List: see every key on the account.
Revoke: delete a key so it can no longer be used.

Figyelem

An API key's secret is shown only once, at the moment it's created. Copy it then and store it somewhere safe. If you lose it, you can't see it again. Just revoke that key and make a new one.

Figyelem

A key must be scoped to a persona (and engine) before it can serve live traffic. An unscoped, account-wide key is rejected on live calls. Provision a scoped key, or link an existing one, first.

Go-live checklist

When all four are true, you're live:

Persona ready: identity and photos set up.
Engine linked: the engine wired to that persona and committed in the Wiring Lab.
A scoped API key: provisioned (or linked) to that exact persona and engine.
Point your bot at the handshake: your integration sends each inbound message to the live handshake endpoint, passing the key in the X-API-Key header. FluidTalk replies with the next message and action to take.

For the exact endpoints, request fields and responses, see the Developer API reference.

Tipp

You don't have to go live to try it. Run the whole conversation in the built-in simulator first (same engine, no key and no real traffic) then wire it up once it behaves the way you want.

Figyelem

Live serving requires an active paid plan. A free or lapsed account is refused at the handshake, so your bot stops serving the moment the plan ends. See Billing & plans.

Related guides

Engine builder: design the conversation before you wire it.
Testing in the simulator: try the engine end-to-end with no key.
Developer API reference: the exact handshake calls and headers.
Billing & plans: what a paid plan unlocks for live serving.