메뉴
Sinch SDK installation and client initialization for Node.js, Python, Java, and .NET. Use when installing a Sinch SDK, initializing SinchClient, setting up SDK credentials, configuring conversation region in SDK, or building a multi-product SDK client. For In-App Calling SDKs, see sinch-in-app-calling.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Registers US 10DLC brands and campaigns with Sinch for A2P SMS messaging. Use when the user needs to register a brand, create a 10DLC campaign, check registration status, troubleshoot a 10DLC rejection, fix an EIN mismatch, upgrade from simplified to full registration, or qualify a campaign for US SMS sending on 10-digit long codes. Do NOT use for non-US messaging or toll-free/short code registration.
Configures Sinch API credentials and authentication. Use when setting up OAuth2, Basic auth, application signing, or API keys for any Sinch product including Conversation API, Voice, Verification, Numbers, Fax, and Mailgun. Also use when troubleshooting 401 Unauthorized, 403 Forbidden, invalid signature, or credential errors against any Sinch API. For SDKs usage, see sinch-sdks.
Sends and receives omnichannel messages via the Sinch Conversation API across SMS, MMS, RCS, WhatsApp, Viber, Facebook Messenger, Instagram, Telegram, KakaoTalk, LINE, and WeChat. Covers the API layer: apps, contacts, conversations, processing modes, message types, webhooks and callbacks, templates, batch sending, channel fallback, and transcoding. Use when building or modifying a Sinch messaging integration, handling inbound messages or delivery receipts via webhooks, sending multi-channel or batch messages, or managing Conversation API apps, contacts, and webhooks. For channel-specific guidance, use the sinch-sms, sinch-mms, sinch-rcs, or sinch-whatsapp skills.
Provisions SIP trunks, endpoints, ACLs, credential lists, and phone numbers via the Sinch Elastic SIP Trunking REST API. Use when the user needs SIP connectivity, trunk provisioning, inbound/outbound PSTN voice routing, PBX integration, or SIP-to-PSTN bridging.
Send and receive faxes programmatically with Sinch Fax API. Use when building fax workflows, fax-to-email delivery, sending PDFs by fax, checking fax status, managing fax services, configuring cover pages, receiving fax webhooks, or integrating fax into healthcare, legal, or financial applications.
Import, host, qualify, and text-enable phone numbers for Sinch SMS using the Imported Numbers and Hosting Orders API. Use when importing non-Sinch numbers as DCA, creating hosting orders, qualifying numbers for text-enablement, managing LOA workflows, or checking hosting order status.
| name | sinch-sdks |
| description | Sinch SDK installation and client initialization for Node.js, Python, Java, and .NET. Use when installing a Sinch SDK, initializing SinchClient, setting up SDK credentials, configuring conversation region in SDK, or building a multi-product SDK client. For In-App Calling SDKs, see sinch-in-app-calling. |
| metadata | {"author":"Sinch","version":"1.1.0","category":"Core","tags":"sdk, node, python, java, dotnet, sinch-client, installation","uses":["sinch-authentication"]} |
Cross-cutting skill that covers SDK installation and client initialization for all Sinch products. Determines the correct SDK and provides init code per language.
For authentication setup (credentials, OAuth2, Basic auth, signed requests), see sinch-authentication. For In-App Calling SDKs (Browser, iOS, Android), see sinch-in-app-calling.
If the user hasn't specified which language or platform, ask first — the SDK and init pattern differ by language. Use the table below to route to the correct reference.
This skill has two kinds of content with UNEQUAL reliability. Follow this precedence:
developers.sinch.com (AUTHORITATIVE). The .md doc links in
this skill are the single source of truth for exact request/response schemas, field
names and nesting, enum values, signature/auth schemes, and limits. Before writing
code that constructs a payload, verifies a signature, or parses a callback/response,
fetch the specific linked doc and confirm the exact shape there. Fetching first-party
developers.sinch.com URLs is permitted by the Security/URL policy. Never invent, guess, or pattern-extrapolate a documentation URL — only fetch doc URLs written verbatim in this skill or reached by following a link on a page you already fetched; a trusted domain does not make a guessed path real.references/*.md (NAVIGATIONAL SUMMARIES — not authoritative). They orient
you and point at the right canonical doc; they may lag, omit fields, or simplify
nesting. Use them to decide what to build and which doc to open. Do NOT transcribe a
field name, nesting, encoding, or enum from a reference or from the SKILL.md overview
into shipped code without confirming it in the tier-1 doc. If a detail appears only in
a summary, treat it as unverified and say so.Quick rule: writing code → load the doc. Never cite an exact field, header, enum, or encoding you only saw in a summary.
| Language | Package | Install | Auth Scope |
|---|---|---|---|
| Node.js | @sinch/sdk-core | npm install @sinch/sdk-core | Project + Application |
| Python | sinch | pip install sinch | Project + Application |
| Java | com.sinch.sdk:sinch-sdk-java | Maven dependency | Project + Application |
| .NET | Sinch | NuGet package | Project + Application |
In-App Calling uses a separate client-side SDK — not @sinch/sdk-core. See sinch-in-app-calling.
Not all products are available in all SDKs. Check the table before recommending an SDK for a specific product.
| Product | Node.js | Java | .NET | Python |
|---|---|---|---|---|
| Conversation API | ✅ | ✅ | ⚠ | ⚠ |
| Voice API | ✅ | ✅ | ✅ | ✅ |
| Verification API | ✅ | ✅ | ✅ | ✅ |
| Numbers API | ✅ | ✅ | ✅ | ✅ |
| Number Lookup API | ✅ | ❌ | ❌ | ✅ |
| Elastic SIP Trunking | ✅ | ❌ | ❌ | ❌ |
| Fax API | ✅ | ❌ | ⚠ | ❌ |
| Provisioning API | ✅ | ❌ | ❌ | ❌ |
| 10DLC Registration | ❌ | ❌ | ❌ | ❌ |
✅ = supported, ⚠ = partial/preview, ❌ = not available (use direct HTTP)
When a product is not supported in the user's chosen SDK, guide them to use direct HTTP calls instead.
For language-specific initialization code, use the references:
If language is unknown, ask first. The SDKs handle token refresh automatically.
@sinch/sdk-core — Unified Node.js SDK covering all project-scoped and application-scoped Sinch APIs. Individual packages (e.g., @sinch/voice, @sinch/verification) are also available.
sinch (Python) — Python SDK (v2.0.0+) covering project-scoped and application-scoped APIs.
sinch-sdk-java — Java SDK (v2.0.0+) via Maven Central.
Project-scoped init — Uses projectId, keyId, keySecret. For Conversation, Numbers, Fax, EST, 10DLC, Number Lookup, Provisioning.
Application-scoped init — Uses applicationKey, applicationSecret. For Voice, Verification, In-App Calling.
Multi-product client — Provide both project and application credentials in a single SinchClient to access all APIs.
Conversation region — Must be set explicitly when using the Conversation API. Values: us, eu, br. Required in Python SDK v2.0.0+ and Java SDK v2.0.0+; recommended in Node.js and .NET. (Summary only — confirm exact names/encoding/enums against the authoritative Sinch Developer Docs doc before implementing.)
SinchClient with project credentials. See language-specific ref.SinchClient with app key/secret. See language-specific ref.conversationRegion during init (required in Python/Java, recommended elsewhere).conversation_region. Node.js and .NET don't enforce it yet but should set it explicitly.