Open API

Sellers Commerce Open API's are accessible by as base url which looks like
api.sellerscommerce.com/api/Shopper/getall

All requests must be made with https. Both request body data and response data are formatted as JSON. Every request, including JSON, must have a Content-Type Http Request Header with a value of application/json.

For example:
Header :
Content-Type: application/json
Authorization: bearer accesstoken

The Sellers Commerce Open API uses a standard Authorization header to identifies every request.
it is also used to track overall call usage. To get access to sellers commerce open api user need to get acess token from our token endpoint
api.sellerscommerce.com/token
Token endpoint need three required data as below :
grant_type : password (no need to change anything, pass as usual)
username : Users Access Key
password : Users Shared Secret Key

With the above informations, user will get below response

{
"access_token": "ux6UKvImExGMm7rzLZDwpZAZPBapSPqNshe9Xx7xpz3HQy5LA5_IL8nu_yEZ_aN-AxjAud6IfvqLEwmFQpC4S8A5k",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "83895c3b-d59f-420e-b67a-8ca6ce3a17b4"
}
please do remember that bearer access token is valid for 1 hr,
However bearer access token can always be regenerated by hitting our refresh token endpoint till 4 hrs with the same Token endpoint api.sellerscommerce.com/token
this time it needs only two required data as below :
grant_type : refresh_token (no need to change anything, pass as usual)
refresh_token : 83895c3b-d59f-420e-b67a-8ca6ce3a17b4 ( it is your previous generated refresh token)

With the above informations, user will get below response

{
"access_token": "KlzDRDd4036-GeczoDjgH1290Q--u5PrYdzxdRjMJUFo-0batdjypjXMO4rkRG2Vxw7fVNU9AyjFsLE421YnnywmtWnHwG8",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "1e1e2f48-824f-44fc-ac09-18f790acfb74"
}

Everytime it will provide you new refresh token which is valid for next 4 hrs. so, you need to get access token by ur privet secret credentials only once and then our endpoint will always provide you new refresh token and access token without asking your secret credential, it also kept our api very secure

Once user have his access token, it needs to be passed with every request as a valid bearer token in the Authorization header:

Header :
Authorization: bearer accesstoken

An endpoint's name indicates the type of data it handles and the action it performs on that data. We are using below actions only:

Action	HTTP	Method Description
Create	POST	Creates an entity of the corresponding type.
Retrieve	GET	Returns all instances of a particular entity that match query parameters you provide.
Delete	DELETE	Deletes the existing entity that matches the identifier you provide. Deleted entities cannot be retrieved.

Requests to Connect Sellers Commerce Open API endpoints must include the following HTTP headers:
Accept: application/json
Authorization: bearer accesstoken

In the place of YOUR_API_KEY, provide either your application's personal access token (available from the application dashboard) or an access token you generated with the OAuth API.

POST requests must include one additional header:
Content-Type: application/json
Authorization: bearer accesstoken

By default, all endpoint responses provide data as JSON in the response body and include a Content-Type: application/json header.

The Sellers Commerce Open API currently only support JSON format.
Data is returned using JSON, a lightweight serialization language that is compatible with many different languages.
JSON is Java Script Object Notationa.
This might be extended in the future which will provide you more output formats based on your request header specification.
For now JSON is the default.
Each API response is wrapped in a standard structure that holds the results of the API call, plus metadata about the request:

[{
"FirstName": "sample string 1",
"LastName": "sample string 2",
"DOB": "2016-04-27T14:38:17.1709364+00:00",
"Deleted": true,
"ShopperTypeID": 11,
"Address": [{
"AddressName": "sample string 1",
"AddressLine1": "sample string 3",
"City": "sample string 5",
"StateCode": "sample string 6",
"CountryCode": "sample string 7",
"ZipCode": "sample string 8"
}]
}]

Sellers Commerce get all api endpoint also support most commonly used odata Queries which are available these days for generic query:

Odata Query Examples
* To get order data between two different order placed date the query should be like
http://api.sellerscommerce.com/api/order/getall?$filter=OrderPlacedDate+gt+datetime'2016-01-01'+and+OrderPlacedDate+lt+datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=CreatedDate ge datetime'2016-01-01' and CreatedDate le datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=ModifiedDate ge datetime'2016-01-01' and ModifiedDate le datetime'2016-06-01'
The above query is an example that how to add odata query after api/order/getall to filter order between 2016-01-01 and 2016-06-01 dates.

You can query any date which is present for the requested method as an example here it's like for order it is OrderPlacedDate
Please remember that OdataQuery requests must include these additional query line other wise it will return you null values
To get order data in orderby

http://api.sellerscommerce.com/api/order/getall?$orderby=OrderNumber desc
Returns all order in descending order number
in the same way other getall methods can be order by valid data which are getting rendered by api

Error Messages
When the SellersCommerce Open API returns error messages, it does so in JSON format. For example, an error response might look like this:
{
"Results": "OrderNotExist",
"ResponseMessage": "Order Does Not Exist",
"StatusCode": 24
}

In addition to descriptive error text, error messages contain machine-parseable codes. While the text for an error message may change, the codes will stay the same. The following table describes the codes which may appear when working with the API:

Sellers Commerce Response Code	Response Body Text/Results	Response Messages	HTTP Status Code	HTTP Status Message
20	Processed	Processed Successfully	200	OK
21	ProviderNotExists	Provider Does Not Exist	404	NotFound
22	UserNotExists	User Does Not Exist	404	NotFound
24	OrderNotExist	Order Does Not Exist	404	NotFound
25	SkuNotExist	Order item with provided SKU Code Does Not Exist in current order	404	NotFound
26	InvalidQty	Shipment quantity is more than quantity to be shipped.	406	NotAcceptable
27	PaymenExist	Payment data already exist for requested order	406	NotAcceptable
28	AlreadyCaptured	Requested Order alredy captured	406	NotAcceptable
29	ProcessFailed	Process gets failed due to some internal errors	406	NotAcceptable
30	InvalidData	Invalid data provided	406	NotAcceptable
31	CategoryNotExist	Category doesn't exists	406	NotAcceptable
32	ParentCategoryNotExists	Parent Category doesn't exists	406	NotAcceptable
33	Exists	Already exists for current request	406	NotAcceptable
34	InvalidSku	Invalid SKU Data Provided	406	NotAcceptable
35	BrandNotExists	Brand and First level category does nor match, Brand Does not exist in our database, Please provide the correct brand name or include it in category if new	406	NotAcceptable
36	InsertCategoryFailed	Category insertion for this product has been Failed, Please try again with valid data	406	NotAcceptable

Sellers Commerce Open API's are accessible by as base url which looks like
api.sellerscommerce.com/api/Shopper/getall

All requests must be made with https. Both request body data and response data are formatted as JSON. Every request, including JSON, must have a Content-Type Http Request Header with a value of application/json.

For example:
Header :
Content-Type: application/json
Authorization: bearer accesstoken

The Sellers Commerce Open API uses a standard Authorization header to identifies every request.
it is also used to track overall call usage. To get access to sellers commerce open api user need to get acess token from our token endpoint
api.sellerscommerce.com/token
Token endpoint need three required data as below :
grant_type : password (no need to change anything, pass as usual)
username : Users Access Key
password : Users Shared Secret Key

With the above informations, user will get below response

{
"access_token": "ux6UKvImExGMm7rzLZDwpZAZPBapSPqNshe9Xx7xpz3HQy5LA5_IL8nu_yEZ_aN-AxjAud6IfvqLEwmFQpC4S8A5k",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "83895c3b-d59f-420e-b67a-8ca6ce3a17b4"
}
please do remember that bearer access token is valid for 1 hr,
However bearer access token can always be regenerated by hitting our refresh token endpoint till 4 hrs with the same Token endpoint api.sellerscommerce.com/token
this time it needs only two required data as below :
grant_type : refresh_token (no need to change anything, pass as usual)
refresh_token : 83895c3b-d59f-420e-b67a-8ca6ce3a17b4 ( it is your previous generated refresh token)

With the above informations, user will get below response

{
"access_token": "KlzDRDd4036-GeczoDjgH1290Q--u5PrYdzxdRjMJUFo-0batdjypjXMO4rkRG2Vxw7fVNU9AyjFsLE421YnnywmtWnHwG8",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "1e1e2f48-824f-44fc-ac09-18f790acfb74"
}

Everytime it will provide you new refresh token which is valid for next 4 hrs. so, you need to get access token by ur privet secret credentials only once and then our endpoint will always provide you new refresh token and access token without asking your secret credential, it also kept our api very secure

Once user have his access token, it needs to be passed with every request as a valid bearer token in the Authorization header:

Header :
Authorization: bearer accesstoken

An endpoint's name indicates the type of data it handles and the action it performs on that data. We are using below actions only:

Action	HTTP	Method Description
Create	POST	Creates an entity of the corresponding type.
Retrieve	GET	Returns all instances of a particular entity that match query parameters you provide.
Delete	DELETE	Deletes the existing entity that matches the identifier you provide. Deleted entities cannot be retrieved.

Requests to Connect Sellers Commerce Open API endpoints must include the following HTTP headers:
Accept: application/json
Authorization: bearer accesstoken

In the place of YOUR_API_KEY, provide either your application's personal access token (available from the application dashboard) or an access token you generated with the OAuth API.

POST requests must include one additional header:
Content-Type: application/json
Authorization: bearer accesstoken

By default, all endpoint responses provide data as JSON in the response body and include a Content-Type: application/json header.

The Sellers Commerce Open API currently only support JSON format.
Data is returned using JSON, a lightweight serialization language that is compatible with many different languages.
JSON is Java Script Object Notationa.
This might be extended in the future which will provide you more output formats based on your request header specification.
For now JSON is the default.
Each API response is wrapped in a standard structure that holds the results of the API call, plus metadata about the request:

[{
"FirstName": "sample string 1",
"LastName": "sample string 2",
"DOB": "2016-04-27T14:38:17.1709364+00:00",
"Deleted": true,
"ShopperTypeID": 11,
"Address": [{
"AddressName": "sample string 1",
"AddressLine1": "sample string 3",
"City": "sample string 5",
"StateCode": "sample string 6",
"CountryCode": "sample string 7",
"ZipCode": "sample string 8"
}]
}]

Sellers Commerce get all api endpoint also support most commonly used odata Queries which are available these days for generic query:

Odata Query Examples
* To get order data between two different order placed date the query should be like
http://api.sellerscommerce.com/api/order/getall?$filter=OrderPlacedDate+gt+datetime'2016-01-01'+and+OrderPlacedDate+lt+datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=CreatedDate ge datetime'2016-01-01' and CreatedDate le datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=ModifiedDate ge datetime'2016-01-01' and ModifiedDate le datetime'2016-06-01'
The above query is an example that how to add odata query after api/order/getall to filter order between 2016-01-01 and 2016-06-01 dates.

You can query any date which is present for the requested method as an example here it's like for order it is OrderPlacedDate
Please remember that OdataQuery requests must include these additional query line other wise it will return you null values
To get order data in orderby

http://api.sellerscommerce.com/api/order/getall?$orderby=OrderNumber desc
Returns all order in descending order number
in the same way other getall methods can be order by valid data which are getting rendered by api

Error Messages
When the SellersCommerce Open API returns error messages, it does so in JSON format. For example, an error response might look like this:
{
"Results": "OrderNotExist",
"ResponseMessage": "Order Does Not Exist",
"StatusCode": 24
}

In addition to descriptive error text, error messages contain machine-parseable codes. While the text for an error message may change, the codes will stay the same. The following table describes the codes which may appear when working with the API:

Sellers Commerce Response Code	Response Body Text/Results	Response Messages	HTTP Status Code	HTTP Status Message
20	Processed	Processed Successfully	200	OK
21	ProviderNotExists	Provider Does Not Exist	404	NotFound
22	UserNotExists	User Does Not Exist	404	NotFound
24	OrderNotExist	Order Does Not Exist	404	NotFound
25	SkuNotExist	Order item with provided SKU Code Does Not Exist in current order	404	NotFound
26	InvalidQty	Shipment quantity is more than quantity to be shipped.	406	NotAcceptable
27	PaymenExist	Payment data already exist for requested order	406	NotAcceptable
28	AlreadyCaptured	Requested Order alredy captured	406	NotAcceptable
29	ProcessFailed	Process gets failed due to some internal errors	406	NotAcceptable
30	InvalidData	Invalid data provided	406	NotAcceptable
31	CategoryNotExist	Category doesn't exists	406	NotAcceptable
32	ParentCategoryNotExists	Parent Category doesn't exists	406	NotAcceptable
33	Exists	Already exists for current request	406	NotAcceptable
34	InvalidSku	Invalid SKU Data Provided	406	NotAcceptable
35	BrandNotExists	Brand and First level category does nor match, Brand Does not exist in our database, Please provide the correct brand name or include it in category if new	406	NotAcceptable
36	InsertCategoryFailed	Category insertion for this product has been Failed, Please try again with valid data	406	NotAcceptable

Sellers Commerce Open API's are accessible by as base url which looks like
api.sellerscommerce.com/api/Shopper/getall

All requests must be made with https. Both request body data and response data are formatted as JSON. Every request, including JSON, must have a Content-Type Http Request Header with a value of application/json.

For example:
Header :
Content-Type: application/json
Authorization: bearer accesstoken

The Sellers Commerce Open API uses a standard Authorization header to identifies every request.
it is also used to track overall call usage. To get access to sellers commerce open api user need to get acess token from our token endpoint
api.sellerscommerce.com/token
Token endpoint need three required data as below :
grant_type : password (no need to change anything, pass as usual)
username : Users Access Key
password : Users Shared Secret Key

With the above informations, user will get below response

{
"access_token": "ux6UKvImExGMm7rzLZDwpZAZPBapSPqNshe9Xx7xpz3HQy5LA5_IL8nu_yEZ_aN-AxjAud6IfvqLEwmFQpC4S8A5k",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "83895c3b-d59f-420e-b67a-8ca6ce3a17b4"
}
please do remember that bearer access token is valid for 1 hr,
However bearer access token can always be regenerated by hitting our refresh token endpoint till 4 hrs with the same Token endpoint api.sellerscommerce.com/token
this time it needs only two required data as below :
grant_type : refresh_token (no need to change anything, pass as usual)
refresh_token : 83895c3b-d59f-420e-b67a-8ca6ce3a17b4 ( it is your previous generated refresh token)

With the above informations, user will get below response

{
"access_token": "KlzDRDd4036-GeczoDjgH1290Q--u5PrYdzxdRjMJUFo-0batdjypjXMO4rkRG2Vxw7fVNU9AyjFsLE421YnnywmtWnHwG8",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "1e1e2f48-824f-44fc-ac09-18f790acfb74"
}

Everytime it will provide you new refresh token which is valid for next 4 hrs. so, you need to get access token by ur privet secret credentials only once and then our endpoint will always provide you new refresh token and access token without asking your secret credential, it also kept our api very secure

Once user have his access token, it needs to be passed with every request as a valid bearer token in the Authorization header:

Header :
Authorization: bearer accesstoken

An endpoint's name indicates the type of data it handles and the action it performs on that data. We are using below actions only:

Action	HTTP	Method Description
Create	POST	Creates an entity of the corresponding type.
Retrieve	GET	Returns all instances of a particular entity that match query parameters you provide.
Delete	DELETE	Deletes the existing entity that matches the identifier you provide. Deleted entities cannot be retrieved.

Requests to Connect Sellers Commerce Open API endpoints must include the following HTTP headers:
Accept: application/json
Authorization: bearer accesstoken

In the place of YOUR_API_KEY, provide either your application's personal access token (available from the application dashboard) or an access token you generated with the OAuth API.

POST requests must include one additional header:
Content-Type: application/json
Authorization: bearer accesstoken

By default, all endpoint responses provide data as JSON in the response body and include a Content-Type: application/json header.

The Sellers Commerce Open API currently only support JSON format.
Data is returned using JSON, a lightweight serialization language that is compatible with many different languages.
JSON is Java Script Object Notationa.
This might be extended in the future which will provide you more output formats based on your request header specification.
For now JSON is the default.
Each API response is wrapped in a standard structure that holds the results of the API call, plus metadata about the request:

[{
"FirstName": "sample string 1",
"LastName": "sample string 2",
"DOB": "2016-04-27T14:38:17.1709364+00:00",
"Deleted": true,
"ShopperTypeID": 11,
"Address": [{
"AddressName": "sample string 1",
"AddressLine1": "sample string 3",
"City": "sample string 5",
"StateCode": "sample string 6",
"CountryCode": "sample string 7",
"ZipCode": "sample string 8"
}]
}]

Sellers Commerce get all api endpoint also support most commonly used odata Queries which are available these days for generic query:

Odata Query Examples
* To get order data between two different order placed date the query should be like
http://api.sellerscommerce.com/api/order/getall?$filter=OrderPlacedDate+gt+datetime'2016-01-01'+and+OrderPlacedDate+lt+datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=CreatedDate ge datetime'2016-01-01' and CreatedDate le datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=ModifiedDate ge datetime'2016-01-01' and ModifiedDate le datetime'2016-06-01'
The above query is an example that how to add odata query after api/order/getall to filter order between 2016-01-01 and 2016-06-01 dates.

You can query any date which is present for the requested method as an example here it's like for order it is OrderPlacedDate
Please remember that OdataQuery requests must include these additional query line other wise it will return you null values
To get order data in orderby

http://api.sellerscommerce.com/api/order/getall?$orderby=OrderNumber desc
Returns all order in descending order number
in the same way other getall methods can be order by valid data which are getting rendered by api

Error Messages
When the SellersCommerce Open API returns error messages, it does so in JSON format. For example, an error response might look like this:
{
"Results": "OrderNotExist",
"ResponseMessage": "Order Does Not Exist",
"StatusCode": 24
}

In addition to descriptive error text, error messages contain machine-parseable codes. While the text for an error message may change, the codes will stay the same. The following table describes the codes which may appear when working with the API:

Sellers Commerce Response Code	Response Body Text/Results	Response Messages	HTTP Status Code	HTTP Status Message
20	Processed	Processed Successfully	200	OK
21	ProviderNotExists	Provider Does Not Exist	404	NotFound
22	UserNotExists	User Does Not Exist	404	NotFound
24	OrderNotExist	Order Does Not Exist	404	NotFound
25	SkuNotExist	Order item with provided SKU Code Does Not Exist in current order	404	NotFound
26	InvalidQty	Shipment quantity is more than quantity to be shipped.	406	NotAcceptable
27	PaymenExist	Payment data already exist for requested order	406	NotAcceptable
28	AlreadyCaptured	Requested Order alredy captured	406	NotAcceptable
29	ProcessFailed	Process gets failed due to some internal errors	406	NotAcceptable
30	InvalidData	Invalid data provided	406	NotAcceptable
31	CategoryNotExist	Category doesn't exists	406	NotAcceptable
32	ParentCategoryNotExists	Parent Category doesn't exists	406	NotAcceptable
33	Exists	Already exists for current request	406	NotAcceptable
34	InvalidSku	Invalid SKU Data Provided	406	NotAcceptable
35	BrandNotExists	Brand and First level category does nor match, Brand Does not exist in our database, Please provide the correct brand name or include it in category if new	406	NotAcceptable
36	InsertCategoryFailed	Category insertion for this product has been Failed, Please try again with valid data	406	NotAcceptable

Sellers Commerce Open API's are accessible by as base url which looks like
api.sellerscommerce.com/api/Shopper/getall

All requests must be made with https. Both request body data and response data are formatted as JSON. Every request, including JSON, must have a Content-Type Http Request Header with a value of application/json.

For example:
Header :
Content-Type: application/json
Authorization: bearer accesstoken

The Sellers Commerce Open API uses a standard Authorization header to identifies every request.
it is also used to track overall call usage. To get access to sellers commerce open api user need to get acess token from our token endpoint
api.sellerscommerce.com/token
Token endpoint need three required data as below :
grant_type : password (no need to change anything, pass as usual)
username : Users Access Key
password : Users Shared Secret Key

With the above informations, user will get below response

{
"access_token": "ux6UKvImExGMm7rzLZDwpZAZPBapSPqNshe9Xx7xpz3HQy5LA5_IL8nu_yEZ_aN-AxjAud6IfvqLEwmFQpC4S8A5k",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "83895c3b-d59f-420e-b67a-8ca6ce3a17b4"
}
please do remember that bearer access token is valid for 1 hr,
However bearer access token can always be regenerated by hitting our refresh token endpoint till 4 hrs with the same Token endpoint api.sellerscommerce.com/token
this time it needs only two required data as below :
grant_type : refresh_token (no need to change anything, pass as usual)
refresh_token : 83895c3b-d59f-420e-b67a-8ca6ce3a17b4 ( it is your previous generated refresh token)

With the above informations, user will get below response

{
"access_token": "KlzDRDd4036-GeczoDjgH1290Q--u5PrYdzxdRjMJUFo-0batdjypjXMO4rkRG2Vxw7fVNU9AyjFsLE421YnnywmtWnHwG8",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "1e1e2f48-824f-44fc-ac09-18f790acfb74"
}

Everytime it will provide you new refresh token which is valid for next 4 hrs. so, you need to get access token by ur privet secret credentials only once and then our endpoint will always provide you new refresh token and access token without asking your secret credential, it also kept our api very secure

Once user have his access token, it needs to be passed with every request as a valid bearer token in the Authorization header:

Header :
Authorization: bearer accesstoken

An endpoint's name indicates the type of data it handles and the action it performs on that data. We are using below actions only:

Action	HTTP	Method Description
Create	POST	Creates an entity of the corresponding type.
Retrieve	GET	Returns all instances of a particular entity that match query parameters you provide.
Delete	DELETE	Deletes the existing entity that matches the identifier you provide. Deleted entities cannot be retrieved.

Requests to Connect Sellers Commerce Open API endpoints must include the following HTTP headers:
Accept: application/json
Authorization: bearer accesstoken

In the place of YOUR_API_KEY, provide either your application's personal access token (available from the application dashboard) or an access token you generated with the OAuth API.

POST requests must include one additional header:
Content-Type: application/json
Authorization: bearer accesstoken

By default, all endpoint responses provide data as JSON in the response body and include a Content-Type: application/json header.

The Sellers Commerce Open API currently only support JSON format.
Data is returned using JSON, a lightweight serialization language that is compatible with many different languages.
JSON is Java Script Object Notationa.
This might be extended in the future which will provide you more output formats based on your request header specification.
For now JSON is the default.
Each API response is wrapped in a standard structure that holds the results of the API call, plus metadata about the request:

[{
"FirstName": "sample string 1",
"LastName": "sample string 2",
"DOB": "2016-04-27T14:38:17.1709364+00:00",
"Deleted": true,
"ShopperTypeID": 11,
"Address": [{
"AddressName": "sample string 1",
"AddressLine1": "sample string 3",
"City": "sample string 5",
"StateCode": "sample string 6",
"CountryCode": "sample string 7",
"ZipCode": "sample string 8"
}]
}]

Sellers Commerce get all api endpoint also support most commonly used odata Queries which are available these days for generic query:

Odata Query Examples
* To get order data between two different order placed date the query should be like
http://api.sellerscommerce.com/api/order/getall?$filter=OrderPlacedDate+gt+datetime'2016-01-01'+and+OrderPlacedDate+lt+datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=CreatedDate ge datetime'2016-01-01' and CreatedDate le datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=ModifiedDate ge datetime'2016-01-01' and ModifiedDate le datetime'2016-06-01'
The above query is an example that how to add odata query after api/order/getall to filter order between 2016-01-01 and 2016-06-01 dates.

You can query any date which is present for the requested method as an example here it's like for order it is OrderPlacedDate
Please remember that OdataQuery requests must include these additional query line other wise it will return you null values
To get order data in orderby

http://api.sellerscommerce.com/api/order/getall?$orderby=OrderNumber desc
Returns all order in descending order number
in the same way other getall methods can be order by valid data which are getting rendered by api

Error Messages
When the SellersCommerce Open API returns error messages, it does so in JSON format. For example, an error response might look like this:
{
"Results": "OrderNotExist",
"ResponseMessage": "Order Does Not Exist",
"StatusCode": 24
}

In addition to descriptive error text, error messages contain machine-parseable codes. While the text for an error message may change, the codes will stay the same. The following table describes the codes which may appear when working with the API:

Sellers Commerce Response Code	Response Body Text/Results	Response Messages	HTTP Status Code	HTTP Status Message
20	Processed	Processed Successfully	200	OK
21	ProviderNotExists	Provider Does Not Exist	404	NotFound
22	UserNotExists	User Does Not Exist	404	NotFound
24	OrderNotExist	Order Does Not Exist	404	NotFound
25	SkuNotExist	Order item with provided SKU Code Does Not Exist in current order	404	NotFound
26	InvalidQty	Shipment quantity is more than quantity to be shipped.	406	NotAcceptable
27	PaymenExist	Payment data already exist for requested order	406	NotAcceptable
28	AlreadyCaptured	Requested Order alredy captured	406	NotAcceptable
29	ProcessFailed	Process gets failed due to some internal errors	406	NotAcceptable
30	InvalidData	Invalid data provided	406	NotAcceptable
31	CategoryNotExist	Category doesn't exists	406	NotAcceptable
32	ParentCategoryNotExists	Parent Category doesn't exists	406	NotAcceptable
33	Exists	Already exists for current request	406	NotAcceptable
34	InvalidSku	Invalid SKU Data Provided	406	NotAcceptable
35	BrandNotExists	Brand and First level category does nor match, Brand Does not exist in our database, Please provide the correct brand name or include it in category if new	406	NotAcceptable
36	InsertCategoryFailed	Category insertion for this product has been Failed, Please try again with valid data	406	NotAcceptable

Sellers Commerce Open API's are accessible by as base url which looks like
api.sellerscommerce.com/api/Shopper/getall

All requests must be made with https. Both request body data and response data are formatted as JSON. Every request, including JSON, must have a Content-Type Http Request Header with a value of application/json.

For example:
Header :
Content-Type: application/json
Authorization: bearer accesstoken

The Sellers Commerce Open API uses a standard Authorization header to identifies every request.
it is also used to track overall call usage. To get access to sellers commerce open api user need to get acess token from our token endpoint
api.sellerscommerce.com/token
Token endpoint need three required data as below :
grant_type : password (no need to change anything, pass as usual)
username : Users Access Key
password : Users Shared Secret Key

With the above informations, user will get below response

{
"access_token": "ux6UKvImExGMm7rzLZDwpZAZPBapSPqNshe9Xx7xpz3HQy5LA5_IL8nu_yEZ_aN-AxjAud6IfvqLEwmFQpC4S8A5k",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "83895c3b-d59f-420e-b67a-8ca6ce3a17b4"
}
please do remember that bearer access token is valid for 1 hr,
However bearer access token can always be regenerated by hitting our refresh token endpoint till 4 hrs with the same Token endpoint api.sellerscommerce.com/token
this time it needs only two required data as below :
grant_type : refresh_token (no need to change anything, pass as usual)
refresh_token : 83895c3b-d59f-420e-b67a-8ca6ce3a17b4 ( it is your previous generated refresh token)

With the above informations, user will get below response

{
"access_token": "KlzDRDd4036-GeczoDjgH1290Q--u5PrYdzxdRjMJUFo-0batdjypjXMO4rkRG2Vxw7fVNU9AyjFsLE421YnnywmtWnHwG8",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "1e1e2f48-824f-44fc-ac09-18f790acfb74"
}

Everytime it will provide you new refresh token which is valid for next 4 hrs. so, you need to get access token by ur privet secret credentials only once and then our endpoint will always provide you new refresh token and access token without asking your secret credential, it also kept our api very secure

Once user have his access token, it needs to be passed with every request as a valid bearer token in the Authorization header:

Header :
Authorization: bearer accesstoken

An endpoint's name indicates the type of data it handles and the action it performs on that data. We are using below actions only:

Action	HTTP	Method Description
Create	POST	Creates an entity of the corresponding type.
Retrieve	GET	Returns all instances of a particular entity that match query parameters you provide.
Delete	DELETE	Deletes the existing entity that matches the identifier you provide. Deleted entities cannot be retrieved.

Requests to Connect Sellers Commerce Open API endpoints must include the following HTTP headers:
Accept: application/json
Authorization: bearer accesstoken

In the place of YOUR_API_KEY, provide either your application's personal access token (available from the application dashboard) or an access token you generated with the OAuth API.

POST requests must include one additional header:
Content-Type: application/json
Authorization: bearer accesstoken

By default, all endpoint responses provide data as JSON in the response body and include a Content-Type: application/json header.

The Sellers Commerce Open API currently only support JSON format.
Data is returned using JSON, a lightweight serialization language that is compatible with many different languages.
JSON is Java Script Object Notationa.
This might be extended in the future which will provide you more output formats based on your request header specification.
For now JSON is the default.
Each API response is wrapped in a standard structure that holds the results of the API call, plus metadata about the request:

[{
"FirstName": "sample string 1",
"LastName": "sample string 2",
"DOB": "2016-04-27T14:38:17.1709364+00:00",
"Deleted": true,
"ShopperTypeID": 11,
"Address": [{
"AddressName": "sample string 1",
"AddressLine1": "sample string 3",
"City": "sample string 5",
"StateCode": "sample string 6",
"CountryCode": "sample string 7",
"ZipCode": "sample string 8"
}]
}]

Sellers Commerce get all api endpoint also support most commonly used odata Queries which are available these days for generic query:

Odata Query Examples
* To get order data between two different order placed date the query should be like
http://api.sellerscommerce.com/api/order/getall?$filter=OrderPlacedDate+gt+datetime'2016-01-01'+and+OrderPlacedDate+lt+datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=CreatedDate ge datetime'2016-01-01' and CreatedDate le datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=ModifiedDate ge datetime'2016-01-01' and ModifiedDate le datetime'2016-06-01'
The above query is an example that how to add odata query after api/order/getall to filter order between 2016-01-01 and 2016-06-01 dates.

You can query any date which is present for the requested method as an example here it's like for order it is OrderPlacedDate
Please remember that OdataQuery requests must include these additional query line other wise it will return you null values
To get order data in orderby

http://api.sellerscommerce.com/api/order/getall?$orderby=OrderNumber desc
Returns all order in descending order number
in the same way other getall methods can be order by valid data which are getting rendered by api

Error Messages
When the SellersCommerce Open API returns error messages, it does so in JSON format. For example, an error response might look like this:
{
"Results": "OrderNotExist",
"ResponseMessage": "Order Does Not Exist",
"StatusCode": 24
}

In addition to descriptive error text, error messages contain machine-parseable codes. While the text for an error message may change, the codes will stay the same. The following table describes the codes which may appear when working with the API:

Sellers Commerce Response Code	Response Body Text/Results	Response Messages	HTTP Status Code	HTTP Status Message
20	Processed	Processed Successfully	200	OK
21	ProviderNotExists	Provider Does Not Exist	404	NotFound
22	UserNotExists	User Does Not Exist	404	NotFound
24	OrderNotExist	Order Does Not Exist	404	NotFound
25	SkuNotExist	Order item with provided SKU Code Does Not Exist in current order	404	NotFound
26	InvalidQty	Shipment quantity is more than quantity to be shipped.	406	NotAcceptable
27	PaymenExist	Payment data already exist for requested order	406	NotAcceptable
28	AlreadyCaptured	Requested Order alredy captured	406	NotAcceptable
29	ProcessFailed	Process gets failed due to some internal errors	406	NotAcceptable
30	InvalidData	Invalid data provided	406	NotAcceptable
31	CategoryNotExist	Category doesn't exists	406	NotAcceptable
32	ParentCategoryNotExists	Parent Category doesn't exists	406	NotAcceptable
33	Exists	Already exists for current request	406	NotAcceptable
34	InvalidSku	Invalid SKU Data Provided	406	NotAcceptable
35	BrandNotExists	Brand and First level category does nor match, Brand Does not exist in our database, Please provide the correct brand name or include it in category if new	406	NotAcceptable
36	InsertCategoryFailed	Category insertion for this product has been Failed, Please try again with valid data	406	NotAcceptable

Sellers Commerce Open API's are accessible by as base url which looks like
api.sellerscommerce.com/api/Shopper/getall

All requests must be made with https. Both request body data and response data are formatted as JSON. Every request, including JSON, must have a Content-Type Http Request Header with a value of application/json.

For example:
Header :
Content-Type: application/json
Authorization: bearer accesstoken

The Sellers Commerce Open API uses a standard Authorization header to identifies every request.
it is also used to track overall call usage. To get access to sellers commerce open api user need to get acess token from our token endpoint
api.sellerscommerce.com/token
Token endpoint need three required data as below :
grant_type : password (no need to change anything, pass as usual)
username : Users Access Key
password : Users Shared Secret Key

With the above informations, user will get below response

{
"access_token": "ux6UKvImExGMm7rzLZDwpZAZPBapSPqNshe9Xx7xpz3HQy5LA5_IL8nu_yEZ_aN-AxjAud6IfvqLEwmFQpC4S8A5k",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "83895c3b-d59f-420e-b67a-8ca6ce3a17b4"
}
please do remember that bearer access token is valid for 1 hr,
However bearer access token can always be regenerated by hitting our refresh token endpoint till 4 hrs with the same Token endpoint api.sellerscommerce.com/token
this time it needs only two required data as below :
grant_type : refresh_token (no need to change anything, pass as usual)
refresh_token : 83895c3b-d59f-420e-b67a-8ca6ce3a17b4 ( it is your previous generated refresh token)

With the above informations, user will get below response

{
"access_token": "KlzDRDd4036-GeczoDjgH1290Q--u5PrYdzxdRjMJUFo-0batdjypjXMO4rkRG2Vxw7fVNU9AyjFsLE421YnnywmtWnHwG8",
"token_type": "bearer",
"expires_in": 3599,
"refresh_token": "1e1e2f48-824f-44fc-ac09-18f790acfb74"
}

Everytime it will provide you new refresh token which is valid for next 4 hrs. so, you need to get access token by ur privet secret credentials only once and then our endpoint will always provide you new refresh token and access token without asking your secret credential, it also kept our api very secure

Once user have his access token, it needs to be passed with every request as a valid bearer token in the Authorization header:

Header :
Authorization: bearer accesstoken

An endpoint's name indicates the type of data it handles and the action it performs on that data. We are using below actions only:

Action	HTTP	Method Description
Create	POST	Creates an entity of the corresponding type.
Retrieve	GET	Returns all instances of a particular entity that match query parameters you provide.
Delete	DELETE	Deletes the existing entity that matches the identifier you provide. Deleted entities cannot be retrieved.

Requests to Connect Sellers Commerce Open API endpoints must include the following HTTP headers:
Accept: application/json
Authorization: bearer accesstoken

In the place of YOUR_API_KEY, provide either your application's personal access token (available from the application dashboard) or an access token you generated with the OAuth API.

POST requests must include one additional header:
Content-Type: application/json
Authorization: bearer accesstoken

By default, all endpoint responses provide data as JSON in the response body and include a Content-Type: application/json header.

The Sellers Commerce Open API currently only support JSON format.
Data is returned using JSON, a lightweight serialization language that is compatible with many different languages.
JSON is Java Script Object Notationa.
This might be extended in the future which will provide you more output formats based on your request header specification.
For now JSON is the default.
Each API response is wrapped in a standard structure that holds the results of the API call, plus metadata about the request:

[{
"FirstName": "sample string 1",
"LastName": "sample string 2",
"DOB": "2016-04-27T14:38:17.1709364+00:00",
"Deleted": true,
"ShopperTypeID": 11,
"Address": [{
"AddressName": "sample string 1",
"AddressLine1": "sample string 3",
"City": "sample string 5",
"StateCode": "sample string 6",
"CountryCode": "sample string 7",
"ZipCode": "sample string 8"
}]
}]

Sellers Commerce get all api endpoint also support most commonly used odata Queries which are available these days for generic query:

Odata Query Examples
* To get order data between two different order placed date the query should be like
http://api.sellerscommerce.com/api/order/getall?$filter=OrderPlacedDate+gt+datetime'2016-01-01'+and+OrderPlacedDate+lt+datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=CreatedDate ge datetime'2016-01-01' and CreatedDate le datetime'2016-06-01'
or http://api.sellerscommerce.com/api/order/getall?$filter=ModifiedDate ge datetime'2016-01-01' and ModifiedDate le datetime'2016-06-01'
The above query is an example that how to add odata query after api/order/getall to filter order between 2016-01-01 and 2016-06-01 dates.

You can query any date which is present for the requested method as an example here it's like for order it is OrderPlacedDate
Please remember that OdataQuery requests must include these additional query line other wise it will return you null values
To get order data in orderby

http://api.sellerscommerce.com/api/order/getall?$orderby=OrderNumber desc
Returns all order in descending order number
in the same way other getall methods can be order by valid data which are getting rendered by api

Error Messages
When the SellersCommerce Open API returns error messages, it does so in JSON format. For example, an error response might look like this:
{
"Results": "OrderNotExist",
"ResponseMessage": "Order Does Not Exist",
"StatusCode": 24
}

In addition to descriptive error text, error messages contain machine-parseable codes. While the text for an error message may change, the codes will stay the same. The following table describes the codes which may appear when working with the API:

Sellers Commerce Response Code	Response Body Text/Results	Response Messages	HTTP Status Code	HTTP Status Message
20	Processed	Processed Successfully	200	OK
21	ProviderNotExists	Provider Does Not Exist	404	NotFound
22	UserNotExists	User Does Not Exist	404	NotFound
24	OrderNotExist	Order Does Not Exist	404	NotFound
25	SkuNotExist	Order item with provided SKU Code Does Not Exist in current order	404	NotFound
26	InvalidQty	Shipment quantity is more than quantity to be shipped.	406	NotAcceptable
27	PaymenExist	Payment data already exist for requested order	406	NotAcceptable
28	AlreadyCaptured	Requested Order alredy captured	406	NotAcceptable
29	ProcessFailed	Process gets failed due to some internal errors	406	NotAcceptable
30	InvalidData	Invalid data provided	406	NotAcceptable
31	CategoryNotExist	Category doesn't exists	406	NotAcceptable
32	ParentCategoryNotExists	Parent Category doesn't exists	406	NotAcceptable
33	Exists	Already exists for current request	406	NotAcceptable
34	InvalidSku	Invalid SKU Data Provided	406	NotAcceptable
35	BrandNotExists	Brand and First level category does nor match, Brand Does not exist in our database, Please provide the correct brand name or include it in category if new	406	NotAcceptable
36	InsertCategoryFailed	Category insertion for this product has been Failed, Please try again with valid data	406	NotAcceptable