A Tringify app is software you run on your own servers that a merchant installs on their store. Once installed, it reads and changes store data through the Store API, receives signed webhooks when things happen, and can add pages to Store Admin and features to the storefront. Checkout and payment stay under Tringify's control: an app can offer a payment method through the provider protocol, but it cannot add to, change or block checkout.
Start here#
Build your first app: create an app, deploy the app starter and install it on a development store, in about half an hour.
Create an app: the choices you make when you create an app, and which ones are permanent.
The app configuration file: every field of
tringify.app.json.How apps are authorized: the credentials an app holds and what each one is for.
Releases and install links: how changes reach stores.
What an app is made of#
Part |
What it is |
|---|---|
Organization |
Owns the app, its credentials and its releases. Organization members build and run it, each within their role. |
Configuration |
Scopes, URLs, events and the features the app adds, kept in |
Listing |
The name, icon, description and support details merchants see. Edited in the Developer Portal. |
Credentials |
A client ID and client secret, and a webhook signing key. |
Releases |
Frozen copies of the configuration that stores install. Editing the draft never changes what stores have. |
Installations |
One per store. Each has its own Store API token and the scopes that store approved. |
What an app can add#
To add |
Read |
|---|---|
Pages inside Store Admin |
|
Features on the storefront |
|
Payment methods or text messaging |
|
A sales channel such as an ads catalog or marketplace |
|
Its own fields on products, orders and other records |
|
Analytics and ads tracking |
|
Paid plans |
To let people sign in to your own website with their Tringify account, without installing anything on a store, read Sign in with Tringify.