> ## Documentation Index > Fetch the complete documentation index at: https://docs.famulor.io/llms.txt > Use this file to discover all available pages before exploring further. # Send from an SMS connection > Send through an owned SMS connection, including an approved company-name RCS connection without a phone number. Omitted delivery mode uses its saved SMS/RCS policy. RCS remains an optional feature of SMS. Sending uses credits; rich/media with SMS fallback requires an explicit text alternative. **Required scope:** `phone_numbers:write`. ## OpenAPI ````yaml /api-reference/openapi.json post /sms/connectors/{id}/send openapi: 3.1.0 info: title: Famulor API version: 1.0.0 description: >- REST API for Famulor. Authenticate with an API key (`fam_...`, created under **Settings → API Keys**) or an OAuth 2.0 access token (`fam_at_...`) as a Bearer token. Every response uses a consistent envelope: `{ "data": ... , "meta": { ... } }` on success and `{ "error": { "code", "message" } }` on failure. List endpoints paginate with `?limit=` (default 50, max 200) and `?offset=`; `meta.pagination.total` carries the total match count. REST operations require API Access through the workspace plan or a recurring add-on. Without it, regular operations return `403 api_access_required`. The invoice-payment and billing-portal operations remain available with a valid `billing:write` credential after a failed plan payment so an authorized owner, admin, or billing member can recover billing. The same customer-facing capabilities are available as MCP tools at `https://app.famulor.io/mcp` (Model Context Protocol, streamable HTTP) using the same credentials, scopes, and workspace access. MCP availability is controlled separately by Connect AI / MCP, not by API Access. servers: - url: https://app.famulor.io/api/v1 description: Hosted platform. - url: https://{domain}/api/v1 description: White-label tenant domain — same paths, tenant branding. variables: domain: default: app.famulor.io description: Your white-label tenant domain. security: - bearerAuth: [] tags: - name: Account description: Self-inspection of the calling credential. - name: Migrations description: Preview and import data from supported legacy platforms. - name: Assistants description: Create and manage voice assistants. - name: Tools description: >- Reusable tools (HTTP APIs and external MCP servers) assistants can call mid-conversation. - name: Voices description: Browse the text-to-speech voice library. - name: Calls description: Start outbound calls and read call history, transcripts and recordings. - name: History description: Unified conversation history across calls, messaging and assistant emails. - name: Campaigns description: Outbound calling campaigns with a compliant power dialer. - name: Leads description: Manage Audience contacts across campaigns, channels and Call QA metrics. - name: Segments description: >- Saved, dynamic lead filters — reusable audience definitions used for Audience search and campaign lead assignment. - name: Suppression description: Cross-channel marketing opt-outs and active workspace suppression records. - name: Callbacks description: >- Scheduled callbacks booked by the Schedule callback tool across voice, chat, and email. - name: Phone Numbers description: Marketplace numbers and customer-provided numbers. - name: Famulor Loop description: >- Personal business-phone access, directory, presence, devices, and Loop call recents. - name: SIP Trunks description: Bring your own SIP provider and numbers. - name: Carrier Connections description: Connect a supported carrier account and import its existing phone numbers. - name: Knowledge Bases description: RAG knowledge bases and documents for assistants. - name: Settings description: Workspace-level settings such as caller-memory defaults. - name: Billing description: Balance and transaction ledger of the API key's workspace. - name: Automations description: >- Native workspace automations — list, create, update, trigger. Requires Automations in the workspace plan. - name: Milian Missions description: Recurring jobs that Milian runs unattended on schedule. - name: Integrations description: >- Calendar integrations (Cal.com, Calendly, Acuity Scheduling, Google Calendar, Outlook, native booking engine). Assign them to assistants to provide availability and booking tools, plus provider-supported appointment lookup, cancellation, and rescheduling. - name: Bookings description: >- Native booking engine — event types with weekly availability, public booking pages at /book/{workspace}/{slug}, and the bookings they produce. - name: Dashboards description: >- Custom analytics dashboards, reusable widgets, and tenant-scoped performance analytics. Requires Custom dashboards in the workspace plan. - name: Catalog description: >- Read-only platform catalogs — available models, supported assistant languages, and prompt templates. - name: Simulations description: Assistant simulation tests (plan-gated). - name: Versions description: Assistant configuration version history. - name: Caller IDs description: Outbound caller ID verification. - name: Widgets description: Web widget connectors. - name: Messaging description: >- Telegram, Slack, and Messenger text bots linked to assistants (Chat SDK). Includes conversation delay, inactivity end, and conversation-ended webhooks. - name: QA description: Cohort AI Quality Assurance runs over call transcripts. - name: White Label description: >- Manage white-label customer accounts, defaults, credit transfers and customer plan offers. Each endpoint documents its required scope and workspace eligibility. - name: API Keys description: >- Self-service API keys for the calling workspace or a same-brand workspace where the credential's user is owner/admin. A key can only mint further keys with a scope subset of its own. - name: Workspaces description: >- List visible workspaces, create an additional workspace for the key owner, and mint a dedicated credential for a selected owner/admin workspace. - name: SMS description: Outbound SMS from workspace phone numbers. - name: Milian description: >- Ask Milian, the AI co-worker in your workspace, and start voice sessions with it. - name: Translation description: >- Live translation sessions that interpret a conversation between two languages. - name: Shopify description: Native Shopify app store connections, assistant tools and activity. - name: Avatars description: Private custom avatars and widget avatar selection. - name: Webhook Subscriptions description: >- Signed workspace event subscriptions, independent of existing destinations. paths: /sms/connectors/{id}/send: parameters: - name: id in: path required: true description: Owned SMS connection ID. schema: type: string format: uuid post: tags: - SMS summary: Send from an SMS connection description: >- Send through an owned SMS connection, including an approved company-name RCS connection without a phone number. Omitted delivery mode uses its saved SMS/RCS policy. RCS remains an optional feature of SMS. Sending uses credits; rich/media with SMS fallback requires an explicit text alternative. **Required scope:** `phone_numbers:write`. operationId: sendSmsFromConnector requestBody: required: true content: application/json: schema: type: object required: - to - body properties: to: type: string description: Recipient in E.164 format. example: '+14155550100' body: type: string minLength: 1 maxLength: 1600 description: >- Message body. RCS allows up to 1,600 Unicode characters. SMS-only sends retain the 1,600 UTF-16-unit limit; channel replies may have a stricter segment limit. delivery_mode: $ref: '#/components/schemas/SmsDeliveryMode' idempotency_key: type: string description: >- Unique request key for one intended send. Reusing it never dispatches again. minLength: 1 maxLength: 128 media_urls: type: array maxItems: 1 items: type: string format: uri pattern: ^https:// maxLength: 2048 description: >- One customer-authorized public HTTPS media URL for RCS. Choose media or rich content. rich_content: $ref: '#/components/schemas/SmsRcsRichContent' sms_fallback_body: type: string description: >- Explicit plain-text SMS alternative required for rich/media content with SMS fallback. For plain-text sends, omit this field or repeat body exactly; a different alternative is rejected. SMS segment counts determine fallback cost (maximum 1,600 UTF-16 units). minLength: 1 maxLength: 1600 description: >- The SMS connection is selected by its path ID; do not provide a second sender in the request body. responses: '201': description: SMS accepted. content: application/json: schema: type: object required: - data properties: data: type: object properties: message_id: type: string format: uuid nullable: true status: type: string credits: type: number transport: type: string enum: - sms - rcs description: >- Known transport for this accepted attempt when available. Final delivery may update later; inspect History for the current delivery state. fallback_used: type: boolean description: >- Whether this attempt used SMS fallback, when transport is known. False is retained explicitly. '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '402': description: Insufficient credits. '403': $ref: '#/components/responses/Forbidden' '429': $ref: '#/components/responses/RateLimited' '503': $ref: '#/components/responses/RequestProtectionUnavailable' components: schemas: SmsDeliveryMode: type: string description: >- Delivery selection within SMS. Omit to inherit the saved connection policy; SMS only prevents RCS upgrade. enum: - sms_only - rcs_preferred - rcs_only SmsRcsRichContent: oneOf: - type: object additionalProperties: false properties: type: type: string enum: - card title: type: string description: Card title. maxLength: 200 body: type: string description: Card message. maxLength: 1600 media_url: type: string description: Public HTTPS image/video URL. format: uri buttons: type: array maxItems: 11 items: $ref: '#/components/schemas/SmsRcsButton' description: 'Up to eleven actions: card buttons and suggested replies.' required: - type description: >- A card needs a title or body and an image or at least one action. Public HTTPS media only; no credentials or private hosts. - type: object additionalProperties: false properties: type: type: string enum: - carousel cards: type: array minItems: 2 maxItems: 10 items: $ref: '#/components/schemas/SmsRcsCard' description: Cards shown in the carousel. required: - type - cards description: >- RCS card or carousel. With SMS fallback, supply an explicit text alternative. SmsRcsButton: oneOf: - type: object additionalProperties: false required: - type - label - value properties: type: type: string enum: - url description: Action type. label: type: string minLength: 1 maxLength: 25 description: Visible action label, in Unicode characters. value: type: string format: uri pattern: ^https:// maxLength: 2048 description: Public HTTPS URL, E.164 number or quick-reply payload. - type: object additionalProperties: false required: - type - label - value properties: type: type: string enum: - phone description: Action type. label: type: string minLength: 1 maxLength: 25 description: Visible action label, in Unicode characters. value: type: string pattern: ^\+[1-9]\d{4,14}$ description: Public HTTPS URL, E.164 number or quick-reply payload. - type: object additionalProperties: false required: - type - label - value properties: type: type: string enum: - reply description: Action type. label: type: string minLength: 1 maxLength: 20 description: Visible action label, in Unicode characters. value: type: string minLength: 1 maxLength: 128 description: Public HTTPS URL, E.164 number or quick-reply payload. description: URL, phone or quick-reply action. Labels count Unicode characters. SmsRcsCard: type: object additionalProperties: false properties: title: type: string description: Card title. maxLength: 200 body: type: string description: Card message. maxLength: 1600 media_url: type: string description: Public HTTPS image/video URL. format: uri buttons: type: array maxItems: 2 items: $ref: '#/components/schemas/SmsRcsButton' description: >- One or two actions, matching the action types and order on every card. minItems: 1 description: >- Carousel card: image, body, one or two actions. Title and body together allow 160 Unicode characters. Every card uses the same action types in the same order. required: - body - media_url - buttons ErrorEnvelope: type: object description: Error envelope returned by every /api/v1 endpoint on failure. required: - error properties: error: type: object required: - code - message properties: code: type: string enum: - unauthorized - forbidden - api_access_required - not_found - invalid_request - rate_limited - conflict - telephony_configuration_error - telephony_unavailable - destination_forbidden - internal_error - service_unavailable - verification_address_required - bundle_address_missing description: >- Stable, machine-readable error code. `service_unavailable` is returned by POST /bookings and GET /booking-event-types/{id}/slots specifically when the availability engine could not be reached (see AvailabilityOrProtectionUnavailable). `verification_address_required` and `bundle_address_missing` are returned by POST /phone-numbers when the verification behind the number has no address (see the operation description). message: type: string description: Human-readable description of the error. reason: type: string description: >- Optional, more specific and stable reason for this error, for example `plan_required`, `read_only_role` or `missing_scope`. Branch on `code` first: `reason` is only present on some errors, and new values may be added. hint: type: string description: >- Optional recovery advice that is safe to show to the end user, for example which settings page to open. responses: BadRequest: description: Invalid request body or parameters. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: invalid_request message: '"to_number" is required (E.164 format, e.g. +4930123456).' Unauthorized: description: Missing, invalid, expired or revoked API key / access token. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: unauthorized message: Invalid API key. Forbidden: description: >- The credential lacks the required scope or role, or the workspace does not have the required capability. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' examples: scopeDenied: summary: Required scope is missing value: error: code: forbidden message: >- This API key is missing the required scope "assistants:write". apiAccessRequired: summary: API Access is not available value: error: code: api_access_required message: >- API Access is not available for this workspace. Review Settings → Plan. RateLimited: description: Too many requests. Retry after the indicated delay. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: rate_limited message: Too many requests. Retry after the indicated delay. RequestProtectionUnavailable: description: Request protection is temporarily unavailable. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: internal_error message: Request protection is temporarily unavailable. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API key description: >- API key (`fam_...`, created under **Settings → API Keys**) or an OAuth 2.0 access token (`fam_at_...`). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as `assistants:read`, `calls:write`, `campaigns:write`, `automations:read`, `dashboards:read`, `dashboards:write`, `leads:write`, `segments:write`, `loop:read`, `loop:write`, `phone_numbers:write`, `sip_trunks:write`, `knowledge:write`, `voices:read`, `billing:read`, `billing:write`, `settings:write`, `platform:read`, `platform:write`; a `*:write` scope implies the matching `*:read`. Automation and dashboard endpoints also accept the legacy `calls:*` scope. Keys without scope restrictions have full access within the workspace's available capabilities. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.