Help me clarify terminology regarding the HTTP API.
Gateway URL and endpoints are the same thing, correct?
This is just the place to make a GET or POST call, correct?
Now for my question. It seams for each of the eBay API has its own gateway.
The Shopping API gate way is http://open.api.ebay.com/shopping?
I'm assuming the fallowing:
Finding: http://open.api.ebay.com/finding?
merchandising: http://open.api.ebay.com/merchandising?
... and so on.
Is this correct? or am I misunderstanding something.
Yes, the end point is the gateway. Each API has its own endpoint/gateway url. You would think that eBay would name their endpoints with the schema you provided, but they didn't. You will need to click on "Making a Call" after selecting the API you want the endpoint for in the documentation.
Example:
Here is the endpoint documentation for the Trading API, Shopping API, and Finding API.
Also you should know that not every endpoint is going to require the same info. For the trading API you are going to need a Token from the seller as well as your APP ID, whereas the shopping and trading API only needs the APP ID.
Related
I need to integrate my website to a third party api "getBooks".This API requires JWT token.I use the "getJWT" api to get the token.My question is whether i need to call getJWT api before every call to getBooks api ? Is there a better way to code this problem?
Website description - It does not have a login feature. Customers can browse books and buy any book without login.JWT is only required by third party for their api.
I'm would like to access my affiliate reports via API? is that possible? I've already made a search on ebay API but I didn't find request for affiliate report.
You can do so, but the functionality is not handled by the eBay Developer program. Instead, you'd request the data from eBay Partner Network. They have a loose "API" for scripting access to your Transaction Download Report.
Follow the instructions for TDR here.
For accessing web-UI reports inside the ePN portal, you might need to scrape them. I think you can at least have un+pw parameters in your login URL. You'll have to look around the ePN site at the link above and see about details like that.
I'm trying to use the WhatsApp API, especially "POST /v1/contacts" at this url "https://developers.facebook.com/docs/whatsapp/api/contacts/".
But actually I don't know which url to use, I tried "https://api.whatsapp.com/v1/contacts" but I got a 404 Not Found Status.
I do my queries on postman.
Has anyone ever used it.
Thank you.
To achieve your goal, you'd need to try a different method because the API you're trying to call is not a public API, it's a private API.
Access private API is only available to verified Whatsapp for Business accounts.
It's Whatsapp For Business service provider you choose and successfully applied for.
My question is similar for Linkedin v2 api: Not enough permissions to access: GET /countriesV2, LinkedIn V2 api: Not enough permissions to access /me GET, Not enough permissions to access /me GET and others, but works with /v2/organizations/ endpoint (that's why I think the app is already applied for api: https://business.linkedin.com/marketing-solutions/marketing-partners/become-a-partner/marketing-developer-program).
That's not my app - my client's one.
My task is getting members' info, but any calls to /v2/people/ endpoint fall.
The r_basicprofile permission is set and I no need for extra profile fields.
Now I see a couple of problems with linkedin REST API:
most of examples are for v1
v1 doesn't work at all
links to the linkedin site (like https://developer.linkedin.com/comment/NNNNN#comment-NNNNN%23comment-NNNNN) mostly don't work (about 95-99%)
I can't even call samples from developer.linkedin.com
I asked about this on linkedin help forum. I don't understand is this api works or not?
Does anyone have a successful experience with /v2/people/ endpoint?
if you really want to use V2 apply to the partnership that is required.
but because you need only basic profile info try this :
https://api.linkedin.com/v1/people/~:(id,first-name,last-name,headline,picture-url,email-address,public-profile-url)?format=json
this will return the information of the person who is loggedin.
if you want information of another person try this:
https://api.linkedin.com/v1/people/[user_id]:(id,first-name,last-name,headline,picture-url,email-address,public-profile-url)?format=json
hopefully this works for you.
Since apparently you're not reachable for API questions via email, I guess I'd have to put all the questions in here since it would be tedious to create one for each of them.
So we're planning on creating a webhooks system for our integrations to create a better experience for our users. There are a few pieces that are missing for our end to support having a Podio integration that runs 100% on webhooks.
Support organization level webhooks instead at the space level.
Send full object payload in the webhooks push so we don't need to fetch the resource again. Or at least provide a delta of changes.
Have a secret token header that you send with each request so we can assure the authenticity of the data (that it's actually from Podio and it's not someone trying to hack our system).
Github does a great job with this: https://developer.github.com/webhooks/#delivery-headers.
Ability to unsubscribe from a webhook if the client revokes the OAuth credentials. Do you automatically delete that webhook or do we need to contact the user or you guys to get rid of it?
Trello for instance deletes all webhooks associated with a token if it's revoked or a second option is our server sends a 410 Gone back and the webhook, well you guessed it, it's gone.
Do you think something like this is feasible in the near future?
Thanks for your insights :)
Seems pretty valid point. Are there any particular org operations that you are interested to have webhooks for? Can you also describe some use-cases for org level webhooks?
Sending full object payload is pretty complicated because items in Podio can be extremely big and it might be not needed for webhook to get all details. That's why we keep it small and tiny and let Podio partners build own complicated solutions based on webhooks.
Secret token is not much needed if there is only item_id sent in webhook. Let's review it on item modified scenario.
1) User (or anything else) modifies item
2) item.modified webhook is triggered with item_id
3) 3rd party app receives webhook
4) 3rd party app makes a call to Podio API (if it's needed) and gets all required information from Podio API
So, if webhook request is fake, then Podio API will return same item details and nothing is affected. If you want to have some extra layer of security: why not making webhook URL unique and specific to webhook? Then only Podio will know which URL to use to trigger this webhook.
Ability to unsubscribe from a webhook if the client revokes the OAuth credentials.
Sorry, but I don't understand your question. Can you please re-phrase it as new StackOverflow question?