API keys, REST endpoints, webhook paths, and ready examples for integrating Yebrax Shops into external systems.
Generate API keys per store and keep permissions scoped to what your integration needs.
Read store details, sync products, fetch orders, and push fulfillment updates.
Payment webhooks, notifications, and outbound automation can sit on a cleaner integration layer.
Give developers a faster path to test before building a full integration.
Give the developer a clean handoff instead of a scattered list of URLs and secrets.
Create a merchant account and generate an API key from the panel.
Use the platform base URL for the API even if the storefront has a custom domain.
Test one read endpoint first, then wire order updates or webhook recipes.
This is the current integration surface after the delivered patch path.
Use these snippets as the starting point before building your production wrapper.
curl -X GET 'https://www.yebrax.shop/api/store/info?slug=demo-store' \ -H 'Authorization: Bearer YOUR_API_KEY'
$ch = curl_init(app_base_url() . "/api/orders?slug=demo-store"); curl_setopt_array($ch, [ CURLOPT_RETURNTRANSFER => true, CURLOPT_HTTPHEADER => ['Authorization: Bearer YOUR_API_KEY'], ]); $json = curl_exec($ch);
const res = await fetch(appBase + "/api/products?slug=demo-store", {
headers: { Authorization: "Bearer YOUR_API_KEY" }
});
const data = await res.json();
import requests\nres = requests.get(app_base + "/api/orders?slug=demo-store", headers={"Authorization":"Bearer YOUR_API_KEY"})\nprint(res.json())
Pair the developers path with the apps marketplace and automation recipes for a cleaner integration handoff.