sondahub / Store API
Store: a fake e-commerce API
An online shop: products, customers, orders, reviews and stock.
Two thousand products in eight categories, eight hundred customers, three thousand orders with their line items, reviews, three warehouses of stock and open carts. Orders move through a lifecycle (pending → paid → shipped → delivered) and the live stream shows orders moving. 20,730 records in all, free over REST, GraphQL, OData, gRPC-Web, SOAP, JSON-RPC, Socket.IO, WebSocket and SSE — no key, no signup.
Connect
- Base URL
- https://api.sondahub.com/v1/store
- OpenAPI 3
- https://api.sondahub.com/v1/store/openapi.json
- GraphQL
- https://api.sondahub.com/v1/store/graphql
- OData
- https://api.sondahub.com/odata/store/
- gRPC-Web
- https://api.sondahub.com/grpc/sondahub.store.v1.StoreService
- .proto
- https://api.sondahub.com/v1/store/store.proto
- SOAP WSDL
- https://api.sondahub.com/soap/store?wsdl
- JSON-RPC
- https://api.sondahub.com/jsonrpc — store.getProduct
- XML-RPC
- https://api.sondahub.com/xmlrpc
- WebSocket
- wss://api.sondahub.com/v1/store/ws
- SSE
- https://api.sondahub.com/v1/store/events
- Socket.IO
- https://api.sondahub.com/store — transports: ['websocket']
- The data
- categories.json, products.json, customers.json, orders.json, order_items.json, reviews.json, warehouses.json, inventory.json, carts.json
In Sonda: Import → From a URL with the OpenAPI address and the whole API lands as a project, one request per operation with example bodies. No keys, no headers to add. More on each protocol.
X-Sondahub-Session: send that token back and the next request sees your write. The server keeps nothing — without the token the world is the seed again. The examples on this page share one session until you reload. More on sessions.curl https://api.sondahub.com/v1/store
Lists and filters
Every list answers { "data": [...], "meta": { "page", "limit", "total", "pages" } } with X-Total-Count and Link headers (next, prev, first, last). These options work on every collection and every nested route:
| Option | Meaning | Example |
|---|---|---|
page, limit | Paging, 1-based; limit 1–200, default 20. offset works too. | ?page=3&limit=50 |
sort | Comma list of fields, - for descending. Default id here. | ?sort=-price,id |
field=value | Equals. Booleans as true/false, null for missing. | ?status=active |
_ne _gt _gte _lt _lte | Not equal and comparisons, on numbers, dates and strings. | ?price_gte=10&price_lt=100 |
_like | Contains, case-insensitive. | ?sku_like=an |
_in | Any of a comma list. | ?id_in=1,2,3 |
_null | true: missing; false: present. | ?slug_null=true |
a.b=value | Inside a JSON field, dotted. | ?address.line1=… |
q | Search across the text fields. | ?q=alpine |
fields | Only these fields back. | ?fields=id,sku |
expand | Embed related records. | ?expand=category,reviews |
paging=cursor, cursor | Cursor paging: meta gains has_more, next_cursor and prev_cursor. starting_after / ending_before take an id, Stripe-style. | ?paging=cursor&limit=50 |
format | The same answer as CSV, XML, YAML, NDJSON or MessagePack — or ask with Accept. | ?format=csv |
A name that is not a field answers 400 and lists the fields. Writes answer 422 with one line per problem, 404 for a missing id, 405 with an Allow header for a verb a route does not take. Any request also takes chaos, a rate limit, an Idempotency-Key and problem+json errors, and any write a signed webhook.
categories
The eight product categories. 8 records — the file, or the categories API page with sample records.
| Field | Type | Notes |
|---|---|---|
idread-only | int | Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed. |
created_atread-only | datetime | When the record was created (ISO 8601, UTC). |
updated_atread-only | datetime | When the record last changed. |
namerequired | string | |
slugrequired | string | |
description | text | |
product_countread-only | int | Seed products in the category. |
Relations: products → the products whose category_id is this category. Use ?expand=products to embed them, or the nested routes.
Endpoints
Try it
curl "https://api.sondahub.com/v1/store/categories?limit=3"
curl https://api.sondahub.com/v1/store/categories/1
curl "https://api.sondahub.com/v1/store/categories/1/products?limit=5"
curl -i -X POST https://api.sondahub.com/v1/store/categories \
-H "Content-Type: application/json" \
-d '{"name":"Audio","slug":"audio"}'
curl "https://api.sondahub.com/v1/store/categories?sort=-id&limit=3" \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
curl -X PATCH https://api.sondahub.com/v1/store/categories/1 \
-H "Content-Type: application/json" \
-d '{"name":"Changed name"}'
curl -X DELETE https://api.sondahub.com/v1/store/categories/9 \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
products
What the store sells. Prices are in USD. 2,000 records — the file, or the products API page with sample records.
| Field | Type | Notes |
|---|---|---|
idread-only | int | Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed. |
created_atread-only | datetime | When the record was created (ISO 8601, UTC). |
updated_atread-only | datetime | When the record last changed. |
skurequired | string | Unique stock keeping unit. |
namerequired | string | |
slug | string | |
description | text | |
category_idrequired | int → categories | |
brand | string | |
pricerequired | float | min 0 |
compare_at_price | float | The struck-through price on sale, or null. |
currency | string | |
color | string | |
weight_g | int | min 0 |
tags | json string[] | |
in_stock | bool | |
ratingread-only | float | Average of the seed reviews, 1–5. |
review_countread-only | int | |
status | enum | active draft archived |
Relations: category → one category through category_id; reviews → the reviews whose product_id is this product; inventory → the inventory whose product_id is this product. Use ?expand=category,reviews,inventory to embed them, or the nested routes.
Endpoints
Try it
curl "https://api.sondahub.com/v1/store/products?status=draft&price_gte=10&expand=category&limit=3"
curl https://api.sondahub.com/v1/store/products/1?expand=category
curl "https://api.sondahub.com/v1/store/products/1/reviews?limit=5"
curl -i -X POST https://api.sondahub.com/v1/store/products \
-H "Content-Type: application/json" \
-d '{"sku":"AUD-4F7K2M","name":"Sonora Wireless Headphones","slug":"sonora-wireless-headphones","category_id":1,"brand":"Sonora","price":149.99,"currency":"USD","color":"Graphite","tags":["bluetooth","travel"],"status":"active"}'
curl "https://api.sondahub.com/v1/store/products?sort=-id&limit=3" \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
curl -X PATCH https://api.sondahub.com/v1/store/products/1 \
-H "Content-Type: application/json" \
-d '{"status":"draft"}'
curl -X DELETE https://api.sondahub.com/v1/store/products/2001 \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
customers
People who buy. Addresses are nested objects; filter on them with a dotted name (?address.country=AR). 800 records — the file, or the customers API page with sample records.
| Field | Type | Notes |
|---|---|---|
idread-only | int | Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed. |
created_atread-only | datetime | When the record was created (ISO 8601, UTC). |
updated_atread-only | datetime | When the record last changed. |
namerequired | string | |
emailrequired | string | |
phone | string | |
company | string | |
address | json { line1, line2?, city, region, postal_code, country } | |
tier | enum | standard silver gold platinum |
marketing_opt_in | bool | |
orders_countread-only | int | |
total_spentread-only | float | |
notes | text |
Relations: orders → the orders whose customer_id is this customer; reviews → the reviews whose customer_id is this customer. Use ?expand=orders,reviews to embed them, or the nested routes.
Endpoints
Try it
curl "https://api.sondahub.com/v1/store/customers?tier=silver&limit=3"
curl https://api.sondahub.com/v1/store/customers/1
curl "https://api.sondahub.com/v1/store/customers/1/orders?limit=5"
curl -i -X POST https://api.sondahub.com/v1/store/customers \
-H "Content-Type: application/json" \
-d '{"name":"Camila Fernandez","email":"[email protected]","tier":"standard"}'
curl "https://api.sondahub.com/v1/store/customers?sort=-id&limit=3" \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
curl -X PATCH https://api.sondahub.com/v1/store/customers/1 \
-H "Content-Type: application/json" \
-d '{"tier":"silver"}'
curl -X DELETE https://api.sondahub.com/v1/store/customers/801 \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
orders
An order and its money. Line items live in order_items (also at /orders/{id}/items and ?expand=items). 3,000 records — the file, or the orders API page with sample records.
items: [{ product_id, quantity }]: the hub prices them from the products, computes subtotal, shipping, tax and total, creates the order items and returns them inline. PATCH to shipped stamps shipped_at and a tracking number; delivered stamps delivered_at.| Field | Type | Notes |
|---|---|---|
idread-only | int | Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed. |
created_atread-only | datetime | When the record was created (ISO 8601, UTC). |
updated_atread-only | datetime | When the record last changed. |
numberread-only | string | Human order number. |
customer_idrequired | int → customers | |
status | enum | pending paid shipped delivered cancelled refunded |
subtotal | float | min 0 |
shipping | float | min 0 |
tax | float | min 0 |
discount | float | min 0 |
total | float | min 0 |
currency | string | |
payment_method | enum | card paypal bank_transfer cash_on_delivery |
shipping_address | json { line1, line2?, city, region, postal_code, country } | |
shipping_method | enum | standard express overnight pickup |
tracking_number | string | |
placed_at | datetime | Defaults to now on POST. |
paid_at | datetime | |
shipped_at | datetime | |
delivered_at | datetime | |
notes | text |
Relations: customer → one customer through customer_id; items → the order items whose order_id is this order. Use ?expand=customer,items to embed them, or the nested routes.
Endpoints
Try it
curl "https://api.sondahub.com/v1/store/orders?status=paid&subtotal_gte=10&expand=customer&limit=3"
curl https://api.sondahub.com/v1/store/orders/1?expand=customer
curl "https://api.sondahub.com/v1/store/orders/1/items?limit=5"
curl -i -X POST https://api.sondahub.com/v1/store/orders \
-H "Content-Type: application/json" \
-d '{"customer_id":1,"status":"paid","currency":"USD","payment_method":"card","shipping_method":"standard","items":[{"product_id":1,"quantity":2}]}'
curl "https://api.sondahub.com/v1/store/orders?sort=-id&limit=3" \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
curl -X PATCH https://api.sondahub.com/v1/store/orders/1 \
-H "Content-Type: application/json" \
-d '{"status":"paid"}'
curl -X DELETE https://api.sondahub.com/v1/store/orders/3001 \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
order items
One product line on an order. 6,219 records — the file, or the order items API page with sample records.
| Field | Type | Notes |
|---|---|---|
idread-only | int | Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed. |
created_atread-only | datetime | When the record was created (ISO 8601, UTC). |
updated_atread-only | datetime | When the record last changed. |
order_idrequired | int → orders | |
product_idrequired | int → products | |
sku | string | |
name | string | The product name at the time of the order. |
quantityrequired | int | min 1, max 999 |
unit_price | float | min 0 |
line_total | float | min 0 |
Relations: order → one order through order_id; product → one product through product_id. Use ?expand=order,product to embed them, or the nested routes.
Endpoints
Try it
curl "https://api.sondahub.com/v1/store/order_items?quantity_gte=1&expand=order&limit=3"
curl https://api.sondahub.com/v1/store/order_items/1?expand=order
curl -i -X POST https://api.sondahub.com/v1/store/order_items \
-H "Content-Type: application/json" \
-d '{"order_id":1,"product_id":1,"quantity":1}'
curl "https://api.sondahub.com/v1/store/order_items?sort=-id&limit=3" \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
curl -X PATCH https://api.sondahub.com/v1/store/order_items/1 \
-H "Content-Type: application/json" \
-d '{"quantity":2}'
curl -X DELETE https://api.sondahub.com/v1/store/order_items/6220 \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
reviews
Customer reviews, 1–5 stars. 2,500 records — the file, or the reviews API page with sample records.
rating and review_count — in the answer’s world, which ends with the answer.| Field | Type | Notes |
|---|---|---|
idread-only | int | Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed. |
created_atread-only | datetime | When the record was created (ISO 8601, UTC). |
updated_atread-only | datetime | When the record last changed. |
product_idrequired | int → products | |
customer_idrequired | int → customers | |
ratingrequired | int | min 1, max 5 |
title | string | |
body | text | |
verified_purchase | bool | |
helpful_votes | int | min 0 |
Relations: product → one product through product_id; customer → one customer through customer_id. Use ?expand=product,customer to embed them, or the nested routes.
Endpoints
Try it
curl "https://api.sondahub.com/v1/store/reviews?rating_gte=1&expand=product&limit=3"
curl https://api.sondahub.com/v1/store/reviews/1?expand=product
curl -i -X POST https://api.sondahub.com/v1/store/reviews \
-H "Content-Type: application/json" \
-d '{"product_id":1,"customer_id":1,"rating":1}'
curl "https://api.sondahub.com/v1/store/reviews?sort=-id&limit=3" \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
curl -X PATCH https://api.sondahub.com/v1/store/reviews/1 \
-H "Content-Type: application/json" \
-d '{"rating":2}'
curl -X DELETE https://api.sondahub.com/v1/store/reviews/2501 \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
warehouses
Where stock sits. 3 records — the file, or the warehouses API page with sample records.
| Field | Type | Notes |
|---|---|---|
idread-only | int | Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed. |
created_atread-only | datetime | When the record was created (ISO 8601, UTC). |
updated_atread-only | datetime | When the record last changed. |
coderequired | string | |
namerequired | string | |
address | json { line1, city, region, postal_code, country } | |
timezone | string |
Relations: inventory → the inventory whose warehouse_id is this warehouse. Use ?expand=inventory to embed them, or the nested routes.
Endpoints
Try it
curl "https://api.sondahub.com/v1/store/warehouses?limit=3"
curl https://api.sondahub.com/v1/store/warehouses/1
curl "https://api.sondahub.com/v1/store/warehouses/1/inventory?limit=5"
curl -i -X POST https://api.sondahub.com/v1/store/warehouses \
-H "Content-Type: application/json" \
-d '{"code":"MIA","name":"A name"}'
curl "https://api.sondahub.com/v1/store/warehouses?sort=-id&limit=3" \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
curl -X PATCH https://api.sondahub.com/v1/store/warehouses/1 \
-H "Content-Type: application/json" \
-d '{"code":"Changed code"}'
curl -X DELETE https://api.sondahub.com/v1/store/warehouses/4 \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
inventory
Stock of a product at a warehouse. 6,000 records — the file, or the inventory API page with sample records.
| Field | Type | Notes |
|---|---|---|
idread-only | int | Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed. |
created_atread-only | datetime | When the record was created (ISO 8601, UTC). |
updated_atread-only | datetime | When the record last changed. |
product_idrequired | int → products | |
warehouse_idrequired | int → warehouses | |
on_handrequired | int | min 0 |
reserved | int | min 0 |
reorder_point | int | min 0 |
bin | string | |
counted_at | datetime |
Relations: product → one product through product_id; warehouse → one warehouse through warehouse_id. Use ?expand=product,warehouse to embed them, or the nested routes.
Endpoints
Try it
curl "https://api.sondahub.com/v1/store/inventory?on_hand_gte=1&expand=product&limit=3"
curl https://api.sondahub.com/v1/store/inventory/1?expand=product
curl -i -X POST https://api.sondahub.com/v1/store/inventory \
-H "Content-Type: application/json" \
-d '{"product_id":1,"warehouse_id":1,"on_hand":1,"bin":"A-14-3"}'
curl "https://api.sondahub.com/v1/store/inventory?sort=-id&limit=3" \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
curl -X PATCH https://api.sondahub.com/v1/store/inventory/1 \
-H "Content-Type: application/json" \
-d '{"on_hand":2}'
curl -X DELETE https://api.sondahub.com/v1/store/inventory/6001 \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
carts
Open shopping carts; items are a nested array, so a cart is one document. 200 records — the file, or the carts API page with sample records.
| Field | Type | Notes |
|---|---|---|
idread-only | int | Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed. |
created_atread-only | datetime | When the record was created (ISO 8601, UTC). |
updated_atread-only | datetime | When the record last changed. |
customer_id | int → customers | |
session_id | string | For anonymous carts. |
status | enum | open abandoned converted |
items | json { product_id, sku, name, quantity, unit_price }[] | |
item_count | int | min 0 |
subtotal | float | min 0 |
coupon | string | |
last_activity_at | datetime |
Relations: customer → one customer through customer_id. Use ?expand=customer to embed them, or the nested routes.
Endpoints
Try it
curl "https://api.sondahub.com/v1/store/carts?status=abandoned&item_count_gte=1&expand=customer&limit=3"
curl https://api.sondahub.com/v1/store/carts/1?expand=customer
curl -i -X POST https://api.sondahub.com/v1/store/carts \
-H "Content-Type: application/json" \
-d '{"status":"open"}'
curl "https://api.sondahub.com/v1/store/carts?sort=-id&limit=3" \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
curl -X PATCH https://api.sondahub.com/v1/store/carts/1 \
-H "Content-Type: application/json" \
-d '{"status":"abandoned"}'
curl -X DELETE https://api.sondahub.com/v1/store/carts/201 \ -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"
WebSocket and SSE
The same stream two ways: the world's own activity, one tick a second, generated for your connection alone. Both push JSON text messages; SSE names each one with event: and numbers it with id:. ?topics=a,b narrows either.
| Topic | What arrives | How often |
|---|---|---|
orders | An order changing status (paid → shipped → delivered). | 4 s |
inventory | A stock level moving at a warehouse. | 6 s |
wss://api.sondahub.com/v1/store/ws?topics=orders
> {"type":"hello","api":"store","topics":[…],"subscribed":[…]}
> {"type":"event","topic":"orders","api":"store","ts":"…","data":{…}}
< {"type":"subscribe","topics":["orders"]} # narrow to some topics
< {"type":"ping"} # → {"type":"pong"}
< anything else # → echoed back as {"type":"echo"}
curl -N "https://api.sondahub.com/v1/store/events?topics=orders"
retry: 3000
id: 1
event: orders
data: {"type":"event","topic":"orders",…}
Socket.IO
The namespace /store on the Socket.IO server at https://api.sondahub.com (path /socket.io/, WebSocket transport): every call over an acknowledgement — getProduct, listProducts and the rest — answered { ok, data } or { ok, error }, and the topics above pushed as events of the same names. Writes keep for the connection, and a session event carries them to the next one. More on the Socket.IO server.
const s = io('https://api.sondahub.com/store', { transports: ['websocket'] })
s.on('orders', (e) => console.log(e))
const { data } = await s.emitWithAck('getProduct', { id: 1 })
GraphQL
One endpoint, https://api.sondahub.com/v1/store/graphql: POST {"query", "variables"} or GET ?query=. Introspection is on, so Sonda's GraphQL mode loads the schema; the SDL is a click away. Every collection is a paged query with the same filter, sort and q options as REST (operators as suffixes: price_lt), a by-id query, relation fields both ways, and create, update, replace and delete mutations — simulated like every write, with the note in extensions.
curl https://api.sondahub.com/v1/store/graphql -H "Content-Type: application/json" -d '{"query": "{ products(limit: 3, sort: \"-id\", filter: { status: active }) { total data { id sku name slug category { name } reviews(limit: 2) { id } } } }"}'
{
products(limit: 3, sort: "-id", filter: { status: active }) {
total
data {
id sku name slug
category { name }
reviews(limit: 2) { id }
}
}
}
OData
The API is also an OData 4.0 service at https://api.sondahub.com/odata/store/: its $metadata, an entity set per collection with the relations as navigation properties, the whole $filter language, nested $expand, $count, $search, paging, writes with ETags and $batch. Power BI and Excel read it as an OData feed. More on OData.
curl -G https://api.sondahub.com/odata/store/products \ --data-urlencode "\$top=3" \ --data-urlencode "\$count=true" \ --data-urlencode "\$expand=category"
gRPC-Web and Connect
The API is also the protobuf service sondahub.store.v1.StoreService, generated from the same registry as REST, so the wire and the docs cannot disagree. The .proto file is one click away; feed it to protoc, buf or your codegen. Calls go to https://api.sondahub.com/grpc/sondahub.store.v1.StoreService/{Method} over gRPC-Web (binary or text) or Connect (JSON or binary; GET for reads). Writes keep to the session like every other write. More on gRPC-Web.
| Method | What |
|---|---|
ListCategories | A page of categories: page, limit, sort, q and filter (field → value, with the REST operator suffixes: price_lt → 20). |
ListProducts | A page of products: page, limit, sort, q and filter (field → value, with the REST operator suffixes: price_lt → 20). |
GetProduct | One product by id. |
CreateProduct | Create a product (simulated, kept in your session token). id and the timestamps are set by the server. |
UpdateProduct | Change the fields set in product (simulated). |
DeleteProduct | Delete one (simulated); answers what was removed. |
ListCustomers | A page of customers: page, limit, sort, q and filter (field → value, with the REST operator suffixes: price_lt → 20). |
ListOrders | A page of orders: page, limit, sort, q and filter (field → value, with the REST operator suffixes: price_lt → 20). |
ListOrderItems | A page of order items: page, limit, sort, q and filter (field → value, with the REST operator suffixes: price_lt → 20). |
ListReviews | A page of reviews: page, limit, sort, q and filter (field → value, with the REST operator suffixes: price_lt → 20). |
ListWarehouses | A page of warehouses: page, limit, sort, q and filter (field → value, with the REST operator suffixes: price_lt → 20). |
ListInventory | A page of inventory: page, limit, sort, q and filter (field → value, with the REST operator suffixes: price_lt → 20). |
ListCarts | A page of carts: page, limit, sort, q and filter (field → value, with the REST operator suffixes: price_lt → 20). |
Watchserver stream | The API's live activity as a server stream, each topic at its own pace: orders (every 4 s), inventory (every 6 s). max_events ends the stream (default 10, at most 120). |
Every collection has List, Get, Create, Update and Delete; the table shows them for products and the lists for the rest.
curl "https://api.sondahub.com/grpc/sondahub.store.v1.StoreService/GetProduct?encoding=json&message=%7B%22id%22%3A1%7D"
curl -X POST https://api.sondahub.com/grpc/sondahub.store.v1.StoreService/ListProducts \
-H "Content-Type: application/json" \
-d '{"limit": 3, "sort": "-id"}'
SOAP, JSON-RPC and XML-RPC
The same five calls per collection, the older ways. SOAP: the service described by its WSDL, document/literal over SOAP 1.1 and 1.2, operations like GetProduct, and a twin behind WS-Security at https://api.sondahub.com/soap/secure/store. JSON-RPC 2.0 at https://api.sondahub.com/jsonrpc and XML-RPC at https://api.sondahub.com/xmlrpc, methods like store.getProduct. Writes keep to the session like every other write. More on SOAP · more on JSON-RPC and XML-RPC.
curl https://api.sondahub.com/jsonrpc \
-H "Content-Type: application/json" \
-d '{"jsonrpc": "2.0", "id": 1, "method": "store.getProduct", "params": [1]}'
curl https://api.sondahub.com/soap/store \
-H "Content-Type: text/xml; charset=utf-8" \
-H 'SOAPAction: "https://sondahub.com/soap/store/GetProduct"' \
-d '<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:s="https://sondahub.com/soap/store">
<soap:Body>
<s:GetProduct><s:id>1</s:id></s:GetProduct>
</soap:Body>
</soap:Envelope>'