Learn how to create custom taps using the Connector Builder
sage-intacct
or chargebee
intacct.com
). This is only used to load a default logostore_name
is a parameter the tenant will configure:
{config.api_key}
x-api-key
header, I’d define the following:
api_key
query parameter (meaning the request will have ?api_key={api_key}
in the URL), I’d define:
username:password
and then base64 encoded.
In many cases, Password will be an empty string, in which case you can leave Password blank. See example below:
Calls
.
Calls
calls
/calls
id
GET
or POST
. In almost all cases this will be GET
application/json
?status=Paid
. This can even reference config parameters if this behavior is configurable
by users:
page
)1
)page
URL parameter, so requests will start from ?page=1
and continue until there is no more data.
offset
)next_offset
)limit
)100
)updated_at
)updated_at[after]
)timestamp
for UNIX timestamps, or a standard date format like %Y-%m-%d %H:%M:%S
started_at
timestamp in the response data, and expects a filter in the URL like: &from=<timestamp>
started_at
field in my
schema to be formatted as a date-time
beause I am using it as the Replication Key:
Sample JSON Schema
/clients
/clients/{client_id}/medical-forms
child_context
– essentially a list of parameters the child streams will have access to in order to make their requests.
parent_stream
: