Cloud and BYOC for Orca Agent Engine are in Private Preview — request an invite
Docs

Sources

Ingest external data into Pulsar with source connectors in Orca Agent Engine on StreamNative Cloud.

A source connector reads from an external system and writes records to a Pulsar topic. Use the connector catalog to discover built-in source types, or deploy a source from an uploaded NAR package.

This resource is a StreamNative Cloud capability served under /apis/cloud.sn.io/v1. A self-hosted engine does not advertise the cloud.sn.io extension group. The ork CLI and TypeScript SDK check GET /apis and report that the capability is unavailable before sending the resource request.

Get your registry endpoint

Registry endpoint

Examples on this page target your registry endpoint - the deployment host root, with no path suffix. For CLI, set ORCA_REGISTRY_URL and exactly one of ORCA_ACCESS_TOKEN (Bearer) or ORCA_API_KEY (x-api-key). For TypeScript SDK, set ORCA_BASE_URL / ORCA_API_KEY (Bearer). To find the endpoint, see Connect to the registry.

Source configuration fields

FieldTypeRequiredDescription
namestringYesSource name. The route also carries this name.
tenant, namespacestringNoPulsar tenant and namespace. The CLI defaults to public/default.
archivestringOne package sourcebuiltin://<type>, an uploaded source:// package, or another package URL.
classNamestringFor custom packagesSource implementation class.
topicNamestringYesDestination Pulsar topic.
connectionstringRequired by the CLI on createWorkspace connection. Immutable after create.
configsobjectConnector-specificFields described by the source catalog.
schemaType, serdeClassNamestringNoOutput schema or SerDe.
parallelismintegerNoSource instances. Defaults to 1 in the CLI.
processingGuaranteesenumNoDelivery guarantee.
resourcesobjectNoCPU, RAM, and disk per instance.
secretsobjectNoSecret mappings consumed by the connector.
snServiceAccountstringNoStreamNative Cloud service account used by the source.

Discover source types

ork sources available-sources -o json
ork sources config-definition data-generator -o json

Create a source

ork sources create \
  --name generated-events \
  --source-type data-generator \
  --destination-topic-name persistent://public/default/events \
  --connection pulsar-main \
  --parallelism 1

Operate sources

OperationCLITypeScriptREST
Listork sources listorca.cloud.connectors.sources.list()GET /apis/cloud.sn.io/v1/connectors/sources
Retrieve configork sources get <name>.retrieve(name)GET .../sources/{name}
Updateork sources update <name>.update(name, params)PUT .../sources/{name}
Deleteork sources delete <name>.delete(name)DELETE .../sources/{name}
Start/stop/restartork sources <action> <name> [instance].start, .stop, .restart and instance variantsPOST .../{name}:<action>
Statusork sources status <name> [instance].retrieveStatus / .retrieveInstanceStatusGET .../{name}/status

Create and update are multipart requests. Use --archive or an uploaded source:// package for a custom NAR. Connection assignment is immutable during updates.

Permissions

Treat every credential that can call the Workspace's cloud.sn.io routes as full access to its sources, and separate access with Workspaces. See Control registry access.

What's next

On this page