Developers
Build on Symplichain from your own code.
Your systems can work with Symplichain through a REST API, webhooks and MCP, the open surfaces of SymConnect™. Create and read records, receive events as they happen, and connect systems we do not list yet.
- REST APIRequest and responseIn production
- WebhooksEvents pushed to youIn production
- MCPTools and custom connectorsAvailable
Documentation is shared with your engineers during onboarding. There is no public documentation portal yet.
- from request to production
- 7 days
- integrations live in production
- 10+
- integrations available through SymConnect
- 40+
Three ways in
Connect your systems through REST, webhooks or MCP.
The REST API reads and writes records on demand, webhooks push events to your endpoint as they happen, and MCP gives agents access to your own tools. The integration in our seven-day story used the API and webhooks.
- In productionRequest and response
REST API
Your backend creates and reads records such as shipments, positions and document status, and gets the answer straight away.
Your backendOn demand - In productionEvents pushed to you
Webhooks
Symplichain calls your endpoint when something changes, such as a shipment status, so your system never has to poll and can start its next step at once.
Status changesNo polling - AvailableTools and custom connectors
MCP
Agents reach your own tools and systems through the Model Context Protocol, including custom connectors for systems we do not list yet.
Custom connectorsAgent tools
Integration surface
Every call works on one shipment record.
Your backend creates shipments, reads their position and documents, and receives status changes, all on one record. The panel is illustrative: the documentation we share during onboarding sets out the exact resources, authentication and limits for your integration.
- One shipment record drives every surface, so your API, web and mobile views read the same data.
- Status changes are pushed to your endpoint as they happen.
- The permissions of each connected system are respected, as they are across the platform.
What you can build
Build tracking and workflows into your own product.
Each of these uses the same integration surface, and our team scopes what your integration needs with yours during onboarding.
Tracking inside your own product
Your backend creates shipments and reads positions and document status, and your web and mobile apps show them from one shipment record.
Read the seven-day storyCustom connectors
A system we do not list yet connects through the API or MCP, so agents read from it and write back to it like any other connected system.
About SymConnectWorkflows your systems start
A call from your system starts a workflow, which runs its steps and closes the loop in the systems of record.
About SymConductorNext steps on your side
Your systems subscribe to status changes and react as soon as they arrive, with no polling and no manual check.
Related
The platform behind the API.
SymConnect™ carries every integration into Symplichain, SymContext™ gives it the operating context and SymTrust™ governs what it can do.
- SymConnectConnectors and open surfaces: REST API, webhooks and MCP, with secure read and write.
- SymContextThe context engine and operations graph behind every answer and action.
- SymTrustPermissions, guardrails and approvals in the path of every agent action.
- Seven-day integrationHow a leading EdTech platform reached production seven days after its request.
- Feature DropRelease notes and what has changed on the platform.
Bring an endpoint and a deadline.
Show us the system you want to connect and what your product needs from it. We will check it against the platform with your engineers.