List Satellite Data Providers by Sensor Type

API Information

• Request Path: /market/satellite/providers
• Request Method: GET

Request Headers

Parameter	Type	Required	Description
Authorization	String	No	Optional; this handler does not read user context—your gateway may still require a token

Request Parameters

None.

Request Example

GET /market/satellite/providers HTTP/1.1

Response Body Structure

CommonResponse Object

Field	Type	Description
code	Integer	Response status code
message	String	Response message
data	SatelliteProvidersResp	Provider mapping grouped by sensor type

SatelliteProvidersResp Object

Field	Type	Description
content	List<SatelliteProvidersItem>	One entry per supported sensor type

SatelliteProvidersItem Object

Field	Type	Description
sensorType	Integer	Sensor type identifier used by the marketplace
providers	List<String>	Provider codes allowed for that sensor type (string ids such as tianyi, changguang)

Response Examples

Success Response

{
  "code": 200,
  "message": "OK",
  "data": {
    "content": [
      {
        "sensorType": 1,
        "providers": ["tianyi"]
      },
      {
        "sensorType": 2,
        "providers": ["changguang"]
      }
    ]
  }
}

Failure Response

{
  "code": 500,
  "message": "Internal server error",
  "data": null
}

Error Code Description

Error Code	Description
200	Success
400	Request parameter error
401	Unauthorized (if enforced externally)
500	Server internal error

Usage Instructions

1. Returns the hard-coded mapping from internal sensorType values to selectable satellite data provider identifiers for programming / ordering flows.
2. Current mapping: sensor type 1 → tianyi; sensor type 2 → changguang.
3. Other providers (for example hongtu) are not included in this response at present—clients should not assume every enum value in code appears here.

Notes

• Values are maintained in application code; changes require a service deployment rather than configuration-only updates.
• Use the returned provider strings consistently with create-order and programming-order APIs that accept a provider field.