Push data to Scowtt's API

If your team has development resources and wants to send records as they happen, Scowtt can provide an API endpoint for your systems to push to. Because each customer's data is shaped differently, it starts with a mapping exercise to align your fields with what Scowtt expects.

How it works: You and Scowtt map your fields together. Scowtt sends you an endpoint and token, your developers build the push, and Scowtt checks a test before you go live.

Before you start

A developer or agency who will build and maintain the push job.
A list of the data you'll send: leads or contacts, activities such as calls, emails and appointments, opportunities or quotes, and purchases or revenue.

What's involved

You: Tell your Scowtt team what you'll send

Share the data list and who on your side is building the push.
You and Scowtt: Map your data fields

You and your Scowtt team map your fields to the expected format: each field you have, what it means and example values. The more complete the mapping, the faster setup goes. Scowtt then does some setup to support your format and shares a timeline.
Scowtt: Send your endpoint and token

Scowtt confirms the payload format and sends your API endpoint and an authentication token through a secure channel.
You: Build the push process

Your team builds the process that sends data to the endpoint: a scheduled batch at least hourly, or each change as it happens.
You: Send a test push

Send a test push and tell your Scowtt team.
Scowtt: Check the test and confirm go-live

Scowtt validates the test push against the mapping, then confirms you can go live.
You: Send your history separately

Send the historical backfill as a one-time transfer through SFTP or a storage bucket. Don't replay years of history through the live API.

Good to know

Give every record a stable ID and an updated-at timestamp, so a record sent twice updates the original instead of creating a duplicate.
Store the token in a secrets manager, not in code.
Tell your Scowtt team before you add, rename or remove fields.
To stop sharing, stop the job. Scowtt revokes the token on request.

Who does what

Step	Who	What changes hands
Tell your Scowtt team what you'll send	You	Your data list and who's building the push
Map your data fields	You and Scowtt	Your field list, meanings and examples
Send your endpoint and token	Scowtt	Endpoint, token, payload format
Build the push process	You	—
Send a test push	You	A test push
Check the test and confirm go-live	Scowtt	Go-live confirmation, or fixes needed
Send your history separately	You	History files, through SFTP or a bucket