Loading Profile...
EMPLOYEE
API endpoint doesn't support paths?
via email
One problem was that the API endpoint is currently at the address http://REDACTED.com/api/private/.
I believe there is currently there is no support for paths in the URL. Correct?
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
-
Inappropriate?You're exactly right that the endpoint does not currently support paths, meaning that you have to put the entire path in your app's API calls. We've been considering whether and when to do this (for a number of reasons) to support the approach you're requesting. This kind of feedback may well tip the scales, thanks!
I’m grateful
-
Inappropriate?I'll keep an eye on this, in the past month I've dealt with 2 apis and both of them had test/beta and production apis. The api service could benefit from the ability to show these three different subdomains and then have the different apis within them. This of course would not be essential to everyone and I wouldn't want to convolute the interface.
I’m hindered from taking advantage of the app.
-
Inappropriate?Those are good points. And yes, not everyone is affected, but here's another example... Twitter is moving its API from twitter.com to api.twitter.com/v1/ ...
Under the current non-path-supporting approach, I'd have to change all my calls in my app or mashup. But if Apigee supported paths, then I could just update my proxy and not have to re-point anything.
It's this kind of feedback that stimulates change, so if anyone else is having this issue, please speak up!
-
Inappropriate?Same here, I aslo use a path for my own made API. I don't really want to change the URL for it.
I’m hindered from taking advantage of the app
-
Inappropriate?Hi all and sorry to reopen this. I am new to apigee and I am a bit confused.
Our API (which we are trying to expose through apigee) is something like:
http://www.threadsy.com/gateway/versi...
Can apigee support such a scheme?
Thanks,
Udi2 Comments
Add a comment
This answers the question
-
Hi Udi, under the current proxy setup, in step 2 you would supply www.threadsy.com as the API Hostname, and choose an Apigee subdomain for your proxy, something like api.threadsy.apigee.com.
In step 3 you'd supply an API method like "gateway/version.json" to test.
Once you finished the proxy setup process, you could call http://api.threadsy.apigee.com/gatewa... and get a response from threadsy.com through the proxy.
At that point you can optionally set up a CNAME record to map a subdomain, such as api.threadsy.com, to that Apigee proxy. See these docs for more info: http://apigee.com/docs/setting_up_dns
We've redesigned the proxy setup screens, and we're working on building them into Apigee in this current development sprint.
We're also planning how to add optional support for paths in the API endpoint, so that you could define "gateway" as part of the path and just use http://api.threadsy.apigee.com/versio... to make the request (or http://api.threadsy.com/version.json in the CNAME example). Is this something you'd like to see?
Let me know if you have any further questions. -
Thanks!
