SelSup Developers

Public API · API Reference

Settings

Endpoints for Settings, including exact routes, parameters, request bodies, and expandable response schemas.

3 endpoints/api/propertyStableMachine-readable description ↗
{ }

This page is backed by an editable standalone contract. Validate write operations with test data before production use.

/api/property

Ready-to-use workflows

Ready-to-use workflows

01

Start using Settings

Use a dedicated API token and validate read operations with test data first.

  1. Keep the token server-side and send it in the Authorization header.
  2. Check required parameters and expand the request or response schema.
  3. Handle the HTTP status and the stable error field in application errors.

Data model

Data structures

Models are listed once here and can also be expanded directly from the endpoints that use them.

Property6 fields
organizationIdinteger · int64

Organization Id.

clientIdinteger · int64

Client Id.

read-only
componentstring

Component.

namestring

Name.

valuestring

Value.

valueNamestring

Value Name.

Error contract

How application errors are returned

The error code is identical in every locale, while the user-facing message is translated by the server. Build application logic around error and use localMessage for display only.

error

Stable machine-readable code for integration logic.

localMessage

Display-ready message in the API token user's language.

params

Values interpolated by the server into the localized message template.

localMessage uses the lang field of the user who owns the API token. The documentation language and Accept-Language header do not change it; Russian is used when the user has no language configured.

RUUser locale is ru
{
  "error": "error_brand_already_exists",
  "localMessage": "Бренд Base уже существует",
  "params": {
    "name": "Base"
  }
}
ENUser locale is en
{
  "error": "error_brand_already_exists",
  "localMessage": "Brand Base already exists",
  "params": {
    "name": "Base"
  }
}

Endpoints

Endpoints

PUT

Put Property

/api/property/
Token with write access

Put Property using PUT /api/property/.

Request body

application/json
Object fieldsProperty
FieldTypeRequiredDescription
organizationId integer · int64 No Organization Id.
clientId integer · int64 No Client Id.
component string No Component.
name string No Name.
value string No Value.
valueName string No Value Name.
curl --request PUT 'https://api.selsup.ru/api/property/' \
  --header 'Authorization: YOUR_API_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "organizationId": 1001,
  "clientId": 1001,
  "component": "string",
  "name": "Example",
  "value": "string",
  "valueName": "Example"
}'

Success response

200

The response has no body.

Errors5

Application errors are normally returned as JSON with error, localMessage, and params. Branch on error; localized text may change. How application errors are returned ↑

401auth_required
Authentication required

Authorization is missing, empty, or contains an invalid token.

400error_access_denied
Insufficient permissions

The token exists, but its role cannot perform this operation.

500error_unknown
Unexpected error

Internal failure. Save the request time and contact support; do not blindly retry a mutation.

400error_invalid_currency_source
The specified currency rate source is not supported

Endpoint-specific error. Use the stable error_invalid_currency_source code in application logic; localMessage contains the translation shown above.

400error_no_client
The client was not found or has been deleted. Write to support

Endpoint-specific error. Use the stable error_no_client code in application logic; localMessage contains the translation shown above.

GET

Get

/api/property/{organizationId}/{component}
Token with read access

Get using GET /api/property/{organizationId}/{component}.

Path parameters

FieldTypeRequiredDescription
organizationId integer · int64 Yes Organization Id.
component string Yes Component.
curl --request GET 'https://api.selsup.ru/api/property/1001/string' \
  --header 'Authorization: YOUR_API_TOKEN'

Success response

200
"string"
Errors7

Application errors are normally returned as JSON with error, localMessage, and params. Branch on error; localized text may change. How application errors are returned ↑

401auth_required
Authentication required

Authorization is missing, empty, or contains an invalid token.

400error_access_denied
Insufficient permissions

The token exists, but its role cannot perform this operation.

500error_unknown
Unexpected error

Internal failure. Save the request time and contact support; do not blindly retry a mutation.

400error_header_logo_upload_failed
Could not upload the logo. Please try again.

Endpoint-specific error. Use the stable error_header_logo_upload_failed code in application logic; localMessage contains the translation shown above.

400error_no_client
The client was not found or has been deleted. Write to support

Endpoint-specific error. Use the stable error_no_client code in application logic; localMessage contains the translation shown above.

400error_ozon_fbo_workflow_not_found
Ozon FBO workflow {id} was not found

Endpoint-specific error. Use the stable error_ozon_fbo_workflow_not_found code in application logic; localMessage contains the translation shown above.

400error_user_does_not_have_this_organization
The user does not have access to this organization

Endpoint-specific error. Use the stable error_user_does_not_have_this_organization code in application logic; localMessage contains the translation shown above.

GET

List

/api/property/list/{component}
Token with read access

List using GET /api/property/list/{component}.

Path parameters

FieldTypeRequiredDescription
component string Yes Component.

Query parameters

FieldTypeRequiredDescription
organizationId integer · int64 No Organization Id.
curl --request GET 'https://api.selsup.ru/api/property/list/string' \
  --header 'Authorization: YOUR_API_TOKEN'

Success response

200
Array item structure Property[]
FieldTypeRequiredDescription
organizationId integer · int64 No Organization Id.
clientId integer · int64 No Client Id.
component string No Component.
name string No Name.
value string No Value.
valueName string No Value Name.
[
  "string"
]
Errors4

Application errors are normally returned as JSON with error, localMessage, and params. Branch on error; localized text may change. How application errors are returned ↑

401auth_required
Authentication required

Authorization is missing, empty, or contains an invalid token.

400error_access_denied
Insufficient permissions

The token exists, but its role cannot perform this operation.

500error_unknown
Unexpected error

Internal failure. Save the request time and contact support; do not blindly retry a mutation.

400error_subscription_expired
Your subscription has expired. Pay the tariff to continue using the service.

Endpoint-specific error. Use the stable error_subscription_expired code in application logic; localMessage contains the translation shown above.

Authorization

Token for test requests

The token stays in this browser's localStorage and is sent only in the Authorization header of requests to api.selsup.ru.

Try it

Real request parameters

Live API response

Send a request to see the SelSup response.