FAQ

How do I connect IXICA mysms to Textable?

IXICA · Integration FAQ · English

How do I connect IXICA mysms to Textable?

Use your IXICA API key and phone number in Textable, then configure the inbound webhook to receive SMS replies.

SMS only: Textable’s IXICA integration currently supports text messages (SMS). MMS is not supported.

What do I need before starting?

  • Access to your IXICA mysms account and its API Key.
  • An IXICA DID assigned to your account with API messaging enabled.
  • Access to your Textable profile.

1. Copy your IXICA API Key

Sign in to IXICA mysms. Open My Account from the letter/profile icon and copy your API Key.

Use the API Key, not the Secret Key. Textable’s IXICA setup instructions use the API key for outbound SMS and webhook configuration; they do not require a Secret field.

2. Enter the details in Textable

Textable field What to enter
API Key The API Key from your IXICA mysms account.
DID / VoIP Phone # The IXICA DID you want to use with Textable. It must be assigned to your IXICA account.

3. Configure the inbound webhook

In IXICA My Account, enter the following in API Webhook URL (SMS), then save the IXICA settings:

https://inbound.textable.app/receive?provider=ixica

Private-label customers: Use the inbound hostname supplied in your Textable onboarding email instead of https://inbound.textable.app. Keep the path and query string /receive?provider=ixica. If you do not have the hostname, contact support@textable.co.

Webhook Type: The linked Textable guide does not specify an IXICA Webhook Type selection. If your portal requires one, confirm the correct type with IXICA rather than copying the 3CX or Yeastar setting.

4. Save and test

  1. In Textable, click Update Profile Details.
  2. Send an SMS from Textable to a mobile phone.
  3. Reply from that phone and confirm that the reply appears in Textable.

How do I update the webhook through the API?

This is an alternative to saving the webhook in the IXICA portal—not an additional step if it is already configured correctly. An administrator can send a POST request to https://mysms.ca/api/webhook with the IXICA API key as a Bearer token and the inbound Textable URL in the form field url.

curl --request POST 'https://mysms.ca/api/webhook' \
  --header 'Authorization: Bearer YOUR_IXICA_API_KEY' \
  --form 'url=https://inbound.textable.app/receive?provider=ixica'

Replace YOUR_IXICA_API_KEY with your own API key. For private-label accounts, replace the inbound hostname as described above. Do not publish or share the completed command with a real key.

A successful webhook update returns application response code 100. This is the code in the API response, not an HTTP status code.

What do the response codes mean?

Code Meaning / next step
000 Invalid API key. Re-copy the API Key from the correct IXICA account.
001 DID not assigned. Check that the number entered in Textable belongs to your IXICA account.
002 API functionality is not enabled on the DID. Contact IXICA to enable API messaging.
100 For an outbound SMS request: SMS sent. For a webhook update: webhook updated successfully.

Sending works, but replies do not appear. What should I check?

Confirm that IXICA’s inbound webhook exactly matches the Textable URL above, or your correct private-label equivalent. Make sure you saved the IXICA settings and clicked Update Profile Details in Textable.

Adapted for IXICA customers from Textable’s IXICA / MySMS Setup Guide, reviewed October 23, 2026. IXICA portal navigation follows the My Account screenshots provided for this FAQ series.

Share

Back to all FAQ answers