Activation status
No TextBee settings loaded yet.
TextBee settings
TextBee activation uses Device ID and API key only.
This settings page has been simplified for 4P3X ClientForge OS™. Enter the TextBee Device ID and API key, activate the connection, then the enquiry page builds the TextBee API endpoint automatically.
Required TextBee inputs
Device ID and API key only. No endpoint URL, webhook URL, label field, service role key, or extra activation settings are required.
How sending works
The enquiry form extracts an E.164 phone number from the contact field and sends the generated brief through the TextBee device using the saved Device ID and API key.
Public deployment note
For a fully public production site, a secure backend function is still the safer option. This static version follows your requested Device ID + API only setup.
device + api flow
TextBee Device + API Enquiry Flow
A simplified 4P3X ClientForge OS™ enquiry pathway using only TextBee Device ID + API key activation, with the API endpoint generated automatically.
