Developers
Build connectors for Bitween.
A connector is a small program that speaks one side of an integration: a receiver, a handler, a mapper or a validator. Write one in the language you know, publish it to the registry, and every Bitween can install it.
Four languages, one shape
The SDK is the same idea everywhere.
Declare the settings the adapter needs, implement the kind’s methods, and hand it to the runner. The CLI embeds every SDK, so a build needs no download.
[AdapterKind("handler")]
[AdapterContract("bitween", 1)]
public class Handler : IBitweenHandler
{
public Handler() => Runner.Expect("ApiKey", isPrivate: true);
public Task<ExchangeFile> Handle(ExchangeFile file) => ...;
}import sw_serverless as sw
from simplyworks_bitween import ExchangeFile, Handler
class AcmeOrders(Handler):
def __init__(self):
sw.expect("ApiKey", secret=True)
def handle(self, file: ExchangeFile) -> ExchangeFile:
...
if __name__ == "__main__":
sw.run(AcmeOrders)import { expect, run } from "@simplyworks/sw-serverless";
import { ExchangeFile, Handler } from "@simplyworks/bitween";
class AcmeOrders extends Handler {
constructor() {
super();
expect("ApiKey", { secret: true });
}
handle(file: ExchangeFile) {
return new ExchangeFile({ ...file });
}
}
run(AcmeOrders);From an idea to the catalogue
Six steps, and a reviewer at the end.
- Step 1
Sign up and claim a namespace
A publisher owns a namespace, and every package id starts with it: acme.orders, acme.sap. Invite your team as owners, maintainers or viewers.
- Step 2
Write it in the browser, or with the CLI
The registry’s workspace is an editor with a file explorer, problems and a build log: nothing to install. Or scaffold with bitween adapter init on your machine.
- Step 3
Build and test
A build runs bitween adapter build in a sandboxed container, then the contract test on the package. Try a command with real settings before you publish.
- Step 4
Sign and publish
From the workspace, the registry’s portal key signs it for you. From CI, your own Ed25519 key signs and a publish token sends it.
- Step 5
Review
Automated checks for the manifest, secrets, vulnerable dependencies and licences, then a Simplify9 reviewer reads the source diff and countersigns.
- Step 6
Listed everywhere
In the catalogue and on the Marketplace tab of every Bitween, with downloads you follow per day from your portal.
Tiers
Who a Bitween trusts by default.
Simplify9’s own connectors and kits, published through the same checks as everyone else’s.
A partner Simplify9 has vetted. Installed by default on every Bitween. Apply from your publisher’s settings.
Everyone who signs up starts here. Installed where an administrator has allowed Community publishers.
Every package carries its source and two signatures. Read how a version gets published at registry.bitween.io/developers
Your connector, on every Bitween.
Sign up to the registry, open a workspace, and have a reviewed, signed package in the catalogue the same week.