SIGNL4 | Operate As Docs

Connect your client's SIGNL4 with a sign-in, and call its API through Operate As.

Website: signl4.com
Connects by: Signing in with SIGNL4
Category: Chat
Services: 1
Tools: 101

Service	Key	Base URL
SIGNL4	`signl4`	`https://connect.signl4.com/api`

Connecting

Your client presses Connect on their link and approves on SIGNL4's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "signl4"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "signl4"    ]  }]

Permissions

What the client reads	Permission it asks for
Stay connected without signing in again	`offline_access`
See your alerts, teams and duty schedules	`public_api_read`
Send and update alerts and change duty schedules	`public_api_write`

Tools

Install SIGNL4's typed package for your language:

pip install operate-as-signl4

pip install operate-as-signl4

Run signl4.delete_categories_team_id_category_id

curl -X POST https://api.operate.as/v1/actions/signl4.delete_categories_team_id_category_id \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "team_id": "<team_id>",
      "category_id": "<category_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/signl4.delete_categories_team_id_category_id \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "team_id": "<team_id>",      "category_id": "<category_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/signl4.delete_categories_team_id_category_id

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://connect.signl4.com/api. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../signl4/..." \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../signl4/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If SIGNL4 refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's SIGNL4 access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's SIGNL4 access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "signl4",
    "services": [
      "signl4"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "signl4",    "services": [      "signl4"    ],    "reconnectUrl": "https://…"  }}