Skip to main content
GET
Get scripts for an integration
Returns every script attached to an integration. The store is bound to your app token server-side, so never send a shop id.

Your app as the integration

An app script belongs to the installation, so an app normally asks for itself. Pass any of these as integrationId and the response lists the scripts your install created:
  • your app id, from GET /app/context at data.app.id
  • your client id, app_<hex>
  • your installation id, from GET /app/context at data.app.installationId
This works on a store with no scripts yet: the id is valid and the array is empty, so you can check before creating anything. It returns the same set as GET /scripts.

A catalog integration

A merchant catalog integration id returns the scripts of that integration. A missing id is 404, an id with no scripts is 200 with an empty array. That difference lets you validate an id before using it.

Response shape

data is an array of scripts. An app script has integration: null and an installation id. A merchant script has an integration id and installation: null.

Authorizations

Authorization
string
header
required

Installed-app access token (prefix app_), issued by the OAuth install flow. The store is bound to the token server-side — never send a shop id.

Path Parameters

integrationId
string
required

Your app id, your client id, your installation id, or a merchant catalog integration id.

Response

Scripts for the integration.

Standard Salesive response envelope. The operation-specific payload is carried in data.

status
integer
required

HTTP status code, echoed in the body.

success
boolean
required

Whether the request succeeded.

message
string
required

Human-readable result message.

data
object[]