Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

call back url is appended to subscriber id? #4

Open
mahoriR opened this issue Sep 22, 2022 · 7 comments
Open

call back url is appended to subscriber id? #4

mahoriR opened this issue Sep 22, 2022 · 7 comments
Labels
question Further information is requested

Comments

@mahoriR
Copy link

mahoriR commented Sep 22, 2022

The postman has callback_urls depicted as following - "callback_url": "/test",

Does this mean callback URLs will be subsciber_id/callback_url?

This will create trouble for TSPs as they will need same callback URLs for multiple subscribers,. @BLR-0118

@mahoriR mahoriR added the question Further information is requested label Sep 22, 2022
@ONDC-Tech
Copy link
Contributor

callback url will be subscriber_id + subscriber_url + callback_url. We wanted to link the callback_url with the domain. How do you propose we do it?

@ONDC-Tech
Copy link
Contributor

@mahoriR

@mahoriR
Copy link
Author

mahoriR commented Sep 26, 2022

I'm not sure why this url be coupled with subsciber_id at all.

Can you please specify - How's this callback_url intended to be used?

@BLR-0118
Copy link
Member

callback_url is only for on_subscribe (for verifying keys using a challenge statement). A TSP will assign an unique subscriber_id to each participant, so you can use the same callback_url with different subscriber_id. Won't this work?

@BLR-0118
Copy link
Member

@mahoriR

@Agam1997
Copy link

Agam1997 commented Jan 5, 2023

@BLR-0118

According to the payload for /subscribe for ops no 1
The payload has a subscriber_url under the network_participant block and a callback_url under the context block.

Swagger hub

According to the subscription docs the ONDC will check https://<subscriber_id>/ondc-site-verification.html for the html file, now will this be https://<subscriber_id>/callback_url/ondc-site-verification.html or https://<subscriber_id>/subsciber_url/ondc-site-verification.html?

For a TSP onboarding, multiple sellers say brand1, brand2, brand3, does each brand must have a separate record on the registry with unique subscriber ids? If so, how can the on_search be implemented to handle all the requests from a single domain?

Let's say the subscriber id for brand1 is "brand1.ondcstore.com" similarly for brand2 "brand2.ondcstore.com" and the TSP implements a "/api/v1/", what would be the BPP_URI on the context object while sending the on_search? Does the TSP send separate on_search requests for each subscribed entity? or it can send a single request with the TSP's subscribed id "TSP.ondcstore.com".

Kindly guide or link documentation. Please let me know if further clarification is needed on my questions.

Thank you!

extedcouD pushed a commit to extedcouD/developer-docs that referenced this issue Jul 26, 2024
@DivyakantSwarnkar01
Copy link

DivyakantSwarnkar01 commented Sep 13, 2024

Can You Please Tell me What is the URL for Changing that mistaken details submitted on staging subscription registry ?

send me answer to ==> [email protected] or +917408765402

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants