Flipkart Notification Integration

Procedure For Notification Configuration in Flipkart
Step 1: Subscribing to Notifications

To use notifications:

• You must be a registered seller on https://seller.flipkart.com.

• Setup a notification receiver in your system. This is an HTTPS server that handles the API notifications triggered when a resource changes. For example: https://www.[your-website].com/notifications-receiver.

• You should have a VAPT certificate for the notification receiver in your system.

Write to seller-api-queries@flipkart.com to subscribe to the notifications. Please provide the following details:

• Seller id / Seller registered email address

• Notification receiver URL

• VAPT certificate for the URL

• If return notifications are needed (Yes / NO)

• If Yes then Notification receiver URL for return notification( This could be same as order notification URL)

• If return notification URL is different then provide VAPT certificate for the URL

• Location ids for which you wants to listen order and return notifications

Step 2: Authentication of Url
All Flipkart Notifications are RESTful notifications that send event payloads to the seller system endpoint.

Sellers authenticate to Flipkart API using OAuth credentials (Application ID and Application Secret). Those who wish to listen to notifications must register their notification endpoints with Flipkart. Sellers need a mechanism to validate whether the request originated from Flipkart and not by untrusted sources. Flipkart REST APIs authenticate to seller notification endpoints using a signature-based authentication by using Authorization headers.

Every notification includes headers in the following format:

Here,

• date_timestamp is the timestamp at which the notification is generated and is in “HTTP-Date” format.

• fk_signature is generated per request using SHA1 based message digest algorithm with values derived from request as:

  SHA-1 (date_timestamp + notification_http_url + notification_http_method + OAuth-secret)

REST endpoints that receive these notifications need to authenticate the request by regenerating the Signature (fk_signature) using the logic above and verifying it with the Authorization (X_Authorization) header. Consider the following example.

Authentication Sample

Step 3: Notification Response:
For notification, the seller application needs to respond with a standard HTTP success status 200, or should throw an error response in the following scenarios only:

• When the seller system is down

• If the payload is incorrect

The notification system ensures that the message is sent at least once, but not only once. Hence, it is recommended to add an idempotency check in the client to avoid processing duplicate notifications.

Step 4: Order Management Notification Reference
Event Received from Flipkart:
1. Shipment Created: Notification sent when an shipment is created in seller system.
Event Body:

2. UnHold: Notification sent after a shipment , which was flagged as Hold, is released for further processing after making relevant verifications.
Attributes
possible value - APPROVED, PACKED

Event Structure:

Step 5: Notification URL Endpoint: where the Create Order Event will Hit (Event mentioned in step 4.1)
Post

Event Received:

Step 6: will Fetch the locationId from the Event and using the locationId I will fetch OtherDetails from DataBase:

Step 7: will combine details fetch from Database and the details fetch from ShipmentCreated Event Given By Flipkart in a Single Map and Publish that to the Middle layer to create Order in Eshopox System through PubSub

Pubsub Sample Event