Skip to main content


Use case

Use case (or integration use case) describes what the business needs from a specific integration. Technically, the use case defines an interface between the application and the integration provider, the schema of input and output (result) data, possible error conditions, and relevant documentation. It is a part of the profile.

For example, the Send SMS Message (SendMessage) use case expects recipient's phone number, sender's phone number, and the text message contents. It will return a message ID as the result.

Use cases are written using the Comlink Profile language, for example:

Send SMS Message
Send single text message
usecase SendMessage unsafe {
input {
"Recipient of the message"
to string

"Sender of the message"
from string

"The text of the message"
text string

result {
"Identifier of Message"
messageId string


A profile contains one or more use cases, along with the version and general documentation for that group of use cases. It is identified by a name, with an optional scope separated by a slash, for example: communication/send-sms. Optionally, the profile can be scoped to a specific version, for example: communication/send-sms@2.0.1. Profiles are versioned with Semantic Versioning to indicate breaking changes.

Profile's file has an extension .supr and it is installed with the Superface CLI. It should be committed to a version control system and kept with the application's code.

Profiles are written using the Comlink Profile language, for example:

Send SMS Message
Send a single SMS message or retrieve its status.

name = "communication/send-sms"
version = "2.0.1"

// First use case definition:
usecase SendMessage unsafe {
// use case body

// Second use case definition:
Message Status
Retrieve status of a sent SMS message
usecase RetrieveMessageStatus safe {
// use case body

// Shared fields and models:
field messageId string

field deliveryStatus enum {


Map defines a provider-specific logic to fulfill the use case, i.e. what API endpoints need to be called, how to format requests and responses, and how authentication is performed.

Maps are fetched by OneSDK at runtime (i.e., when the particular profile is used with the particular provider for the first time) and can be also updated at runtime (e.g., to fix/handle breaking changes in the provider's API).

Map files have an extension .suma, and are written in the Comlink Map language. They specify the name of the provider and the profile, along with its major and minor version. For each use case defined in the respective profile, there is a corresponding map directive inside the map file.

Example of the map for communication/send-sms profile and the provider twilio:

profile = "communication/send-sms@2.0"
provider = "twilio"

map SendMessage {
http POST "/2010-04-01/Accounts/{parameters.accountSid}/Messages.json" {
security "basic"

request "application/x-www-form-urlencoded" {
body {
To =,
From = input.from,
Body = input.text

response 201 "application/json" {
map result {
messageId = body.sid

map RetrieveMessageStatus {
// body of the RetrieveMessageStatus logic


Provider (or integration provider) defines a set of base URLs (services), security schemes, and integration parameters. This information is used for reusability between maps, and as a security measure. Maps cannot send requests outside of defined services, and cannot read values passed to the authentication scheme.

Provider vs. company

From the perspective of Superface, a single provider does not have to correspond to a single company. Large companies, like Google, often have multiple unrelated APIs, each with its own provider (e.g. google-apis-maps or google-apis-computer-vision). Conversely, your provider can specify services from unrelated companies, if you need to use these services in a single map.

Provider definition is a JSON file adhering to the Comlink Provider schema. The provider is configured by the Superface CLI for particular profiles, which enables the respective maps to be used by OneSDK in the runtime. A provider is identified by its name, for example: twilio.

Provider name limitations

Provider name cannot contain numbers to avoid typosquatting attacks. Furthermore, if you are publishing a provider into the registry, its name must start with unverified- prefix, e.g. unverified-twilio. See Verification for further details.

Example of the twilio provider:

"name": "twilio",
"services": [
"id": "default",
"baseUrl": ""
"defaultService": "default",
"securitySchemes": [
"id": "basic",
"type": "http",
"scheme": "basic"
"parameters": [
"name": "accountSid",
"description": "Account security identifier"

Integration parameter

Integration parameters are provider-specific values which can be used in maps and provider definitions. A parameter's value can be specified either via an environment variable, in the super.json file, or at runtime as an argument of the perform() method.

Common uses for integration parameters include:


Registry is a web service for the distribution and discovery of profiles, maps, and providers. The service accepts Comlink files for publishing, and generates Abstract Syntax Tree (AST) for runtime consumption by OneSDK.

The public registry is available at Integrations available in the public catalog are maintained and published from the Station GitHub repository.


OneSDK is a universal API client for Node.js. It is the primary way of using Superface integrations. It can update and execute Comlink files, automatically switch providers, and report integrations' health via built-in monitoring.

For more details, see OneSDK reference and its GitHub repostiory.


super.json is the configuration file used by OneSDK to load profiles, maps, and provider files. By default it is located in superface/super.json. It is managed with Superface CLI.

For more details about the file's content, see super.json reference.

Comlink is a domain-specific language for declarative description of API integrations. It consists of three parts: Profile, Map, and Provider definition. Integrations written with Comlink are consumed by OneSDK.

For more details see Comlink reference.