Build with FMCG Cloud
Five AI-powered APIs for FMCG distribution. RESTful design, HMAC & JWT authentication, real-time webhooks, and comprehensive SDKs. Ship in hours, not months.
Getting Started
Get Your API Key
Sign up for a free account and generate your API credentials from the dashboard. You'll get an API key and HMAC secret for service-to-service authentication.
Make Your First Call
Use the cURL example to call the Shelf Recognition API. Replace the bearer token with your API key and point to any shelf image URL.
curl -X POST https://api.fmcgcloud.com/v1/shelf/analyze \
-H "Authorization: Bearer fmcg_sk_live_..." \
-H "Content-Type: application/json" \
-d '{
"image_url": "https://cdn.example.com/shelf.jpg",
"store_id": "STR-001",
"options": {
"detect_brands": true,
"count_facings": true
}
}'Go to Production
Load credits, configure webhooks for async results, set up sub-accounts if needed, and you're live. No staging environment required — sandbox and production use the same APIs.
Authentication
HMAC Signature
For service-to-service calls, sign requests with HMAC-SHA256. Combine the timestamp and request body, sign with your API secret, and include the signature in the request headers.
const crypto = require("crypto");
const secret = process.env.FMCG_API_SECRET;
const timestamp = Date.now().toString();
const body = JSON.stringify(payload);
const signature = crypto
.createHmac("sha256", secret)
.update(timestamp + body)
.digest("hex");
headers["X-FMCG-Timestamp"] = timestamp;
headers["X-FMCG-Signature"] = signature;JWT Bearer Token
For user-context requests, include a JWT bearer token in the Authorization header. Tokens are issued via the authentication endpoint and include tenant and user scopes.
// Bearer token authentication
const response = await fetch(
"https://api.fmcgcloud.com/v1/shelf/analyze",
{
method: "POST",
headers: {
"Authorization": "Bearer " ,
"Content-Type": "application/json",
},
body: JSON.stringify({ image_url: "..." }),
}
);Product APIs
Sub-Account Architecture
Credit Pooling
Purchase credits at the parent level and allocate them to sub-accounts. Set spending limits, track consumption per sub-account, and top up allocations via API.
Data Isolation
Each sub-account's data is fully isolated — product catalogs, customer lists, and analysis results are never shared. Enforced at the database level, not application logic.
Usage Tracking
Per-sub-account usage reports with credit consumption breakdown by product, operation type, and time period. Export via API for integration with your billing system.
Webhooks & Events
SDKs & Tools
TypeScript SDK
AvailablePython SDK
Coming SoonPostman Collection
AvailableOpenAPI Spec
AvailableRate Limits & SLAs
Developer FAQ
Start Building Today
Get your API credentials in minutes. Full sandbox access. No credit card required.