Custom Systems · Custom APICustom integration — assessment required

Define one useful interface between your system and field work.

Assess a custom connection around the business outcome, data ownership and authorised interfaces. The generic REST adapter is not a production-ready connector. Each custom scope needs implementation and acceptance testing.

Discuss This Integration View Data Scope

Custom API Scope map · proposed connection

Custom APIAuthorised source / destination

Approved master recordsCustom system → SalesTOS

Operational activitySalesTOS → custom system

Status acknowledgementsAgreed directions

SalesTOSCandidate field context

Record ownership and direction are defined below. No universal two-way sync is implied.

The operational need

Why connect these systems?

An internal system may use identifiers that differ from field records.

Two systems editing the same field can create conflicting updates.

A failed or repeated request needs an agreed operational outcome.

Direction, ownership, prerequisites

What data can be exchanged?

Each row is a separate scope decision. Supported workflows still require configuration; proposed records require assessment and implementation.

Custom API data scope
Record or object	Direction	System of record	Purpose	Availability / prerequisites
Approved master records	Custom system → SalesTOS	Agreed external master	Candidate field context	Assessment: documented interface and mapping
Operational activity	SalesTOS → custom system	SalesTOS	Candidate downstream visibility	Assessment: approved fields and destination
Status acknowledgements	Agreed directions	Receiving service	Potential processing feedback	Custom implementation required
Financial transactions	No default writeback	Financial system	Potential separate scope	Explicit validation and approval required

Connection design

How the connection works

Review the documented API or authorised file interface, authentication method and network boundary. Decide whether scheduled reads or an event-driven design fits the requirement. Do not assume unrestricted SalesTOS API access or direct database connectivity.

Illustrative working scenario

From system context to a useful next action.

An internal distributor system could supply an approved customer reference. SalesTOS would hold the field visit and follow-up, while a separately scoped activity acknowledgement could return to the internal system.

What happens to writeback?

Two-way exchange must be designed field by field. Financial posting, deletions and ownership changes are never implied by a basic data feed.

Before implementation

Setup requirements

Interface documentation and non-sensitive sample payloads
System owner and authorised access method
Record identifiers, volume and refresh expectations
Test environment and acceptance criteria

Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.

Operating the agreed scope

Reliability & access

Agree idempotency, retry limits, failure visibility, audit history and permission boundaries. These are requirements to implement, not capabilities of the current generic adapter. Assign an owner for mapping changes and reconciliation.

A clearer scope starts here

Questions, answered.

Search these questions

Custom API integration

Does a REST API mean the connector is ready?

No. Mapping, authentication, failure handling and testing still need implementation.

Can we make it two-way?

Only for explicitly scoped records and fields with clear conflict ownership.

Do you need direct database access?

No such access is assumed. Start with an authorised documented interface.

What should we share first?

A business scenario, interface documentation and redacted example records. Do not send credentials through the enquiry form.

What should we prepare for a Custom API discussion?

Interface documentation and non-sensitive sample payloads; System owner and authorised access method; Record identifiers, volume and refresh expectations; Test environment and acceptance criteria. Share redacted examples through an agreed channel, never passwords or API secrets in the public form.

How is Custom API integration scope confirmed?

Review the objects and prerequisites on this page, then agree mapping, access, refresh timing and acceptance criteria. Two-way exchange must be designed field by field. Financial posting, deletions and ownership changes are never implied by a basic data feed.

Explore the adjacent workflow