Successful requests
Responses include data, pagination where relevant and a request ID that can be used for tracing.

Use the quickstart, endpoint map and request conventions to connect a server-side application to the marketplace API.
Quickstart
Choose the required scopes and keep the secret in your server environment.
Pass the key as a Bearer token and provide platform-specific parameters.
Validate status, use normalized fields and log the request ID for support.
const response = await fetch(
"https://api.atphosting24.com/v1/products/search?q=keyboard&platform=taobao",
{ headers: { Authorization: "Bearer YOUR_API_KEY" } }
);
const data = await response.json();Endpoint map
Availability depends on the selected plan and connector approval.
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /v1/products/search | Search normalized marketplace catalogs |
| GET | /v1/products/{id} | Read product, variation and seller details |
| POST | /v1/products/image-search | Find products from an image |
| POST | /v1/translate | Translate marketplace content |
| POST | /v1/orders | Create a sourcing order |
| GET | /v1/orders/{id} | Read order and fulfilment status |
| GET | /v1/logistics/{tracking} | Read normalized tracking events |
| POST | /v1/webhooks | Register an event destination |
Responses include data, pagination where relevant and a request ID that can be used for tracing.
Use response headers to monitor remaining quota and exponential backoff for retryable responses.
Errors return a stable code, readable message and request ID. Validation errors identify the affected field.
Choose a plan or share the required marketplaces and workflow for guided onboarding.