API overview
FCC (Flipkart Commerce Cloud) Retail Media provides a suite of APIs for ad serving. All endpoints follow consistent conventions for authentication and request structure.
- GetBids APIs: Server-to-server APIs for requesting ad candidates across Sponsored Product Ads, Product Contextual Ads, and Display Ads formats.
Ad formats
Use the FCC Ads Server to Server API to integrate with FCC Ads Manager directly from your server. FCC Retail Media supports three ad formats:
| Ad format | Description |
|---|---|
| Sponsored Product Ads (SPA) | Promoted product listings displayed across different pages. |
| Product Contextual Ads (PCA) | Rich ad format that combines brand banners with product cards. |
| Display Ads (DSP) | Monetise your inventory across web, msite, and app surfaces. Supports banner ads (JSON markup) and video ads (VAST 4.2 XML). |
Authentication
Authenticate your GetBids requests
All GetBids requests require:
| Parameter | Type | Description |
|---|---|---|
| X-AUTH-TOKEN | header | Token to validate clients. Shared post onboarding. |
| client | query | Tenant level identifier. Same as networkId. Provided during onboarding. |
Base URL
https://{domain}
You receive your domain during onboarding.
Endpoint summary
GetBids APIs
| Method | Path | Ad format | Description | Specification |
|---|---|---|---|---|
| POST | /v1/spa/getBids | Sponsored Product Ads | Request sponsored product ad candidates for a given context and placement. | View spec |
| POST | /v1/sba/getBids | Product Contextual Ads | Request product contextual ad candidates for a given context and placement. | View spec |
| POST | /v1/dsp/getBids | Display Ads | Request display ad creatives for a given context and slot. | View spec |
Response codes
| Code | Meaning |
|---|---|
200 | OK. Request succeeded. |
400 | Bad Request. Invalid input or missing required fields. |
401 | Unauthorized. Invalid client or missing X-AUTH-TOKEN or client identifier. |
500 | Internal Server Error. |