Build on FYNXT and keep the boundaries clear.
Technical guidance for APIs, events, webhooks, widgets and integration patterns across the FYNXT platform. Reference documentation comes with API access.
Four ways to build on FYNXT.
Use the approach that fits the job: call a service, listen for a change, embed an experience or reuse a proven connector.
Decide who owns each record.
Before the first call, agree which system is the source of truth for each record and which one orchestrates the journey. A typical split looks like this; your architecture decides.
From request to production.
Access starts with a conversation about what you want to build, so the documentation and environments match the scope.
- 01
Request access
Tell us what you want to connect and why.
- 02
Agree the scope
Decide the records, events and environments involved.
- 03
Build and test
Develop against a non-production environment with the documentation for your scope.
- 04
Go live
Promote the integration under the same change controls as the rest of the platform.
Integrations that stay easy to change.
What to aim for when you build on FYNXT.
Take the next informed step.
Move from this page into the most relevant platform, solution or industry context.
Rather talk it through?
Talk to salesBuild on FYNXT, with the boundaries agreed.
Tell us what you want to connect. We will agree the scope, the environments and the documentation you need.