Get App Proxy List

🔒

Requires read_app_proxy access scope.

The Get App Proxy List retrieves the list of all APP_Proxy instances created by the current requesting APP for the store corresponding to the requested domain name. The default display is the first page, with a default of 20 entries per page, and a maximum of 250 entries.

This API is especially useful for:

  1. Listing all proxy configurations set up for an application within a Shoplazza store.
  2. Monitoring and managing real_path and proxy_url mappings.
  3. Auditing the integration points between the application and Shoplazza.

Request Parameters

Public Request Parameters

📘

Public Request Parameters

Query Parameters

ParameterTypeRequiredDefaultDescriptionExample
pageint32No1Page number.1
limitint32No20Number of records per page. Maximum is 250. A value of -1 retrieves all records.20

Response Explanation

Public Response Parameters

📘

Public Response Parameters

Successful Response Fields

FieldTypeDescriptionExample
app_proxys[]arrayarray of app_proxys
app_proxys[].idintThe unique identifier for the app proxy.32261
app_proxys[].real_pathstringThe real path set for accessing Shoplazza.apps/testappproxy
app_proxys[].proxy_urlstringThe URL for accessing the developer's application.https://shoplazza.feishu.com/okr
app_proxys[].created_atstringThe creation timestamp of the app proxy.2024-12-28T03:51:58+00:00
app_proxys[].updated_atstringThe last updated timestamp of the app proxy.2024-12-28T03:51:58+00:00

Error Response

Error responses in the API can be represented using two different fields: errors and error. Both fields provide details about issues encountered during request processing. Below is an explanation of the fields with their respective examples and descriptions.

FieldTypeExampleDescription
errorsArray[ "file number error"]A list of errors encountered during the request processing.
FieldTypeExampleDescription
errorString "page not found"Indicates an error encountered during the process

Error Detail

Status CodeMessagePossible ReasonExample Response
400Bad RequestInvalid input format or request structure (e.g., missing required fields or incorrect data types).Bad Request
UnauthorizedThe request is missing valid authentication credentials or the credentials provided are invalid.Unauthorized

API Structure Overview

Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!