- Posts: 24
APi on own domain possible?
- dbode
- Topic Author
- Offline
Less
More
7 years 7 months ago #100
by dbode
APi on own domain possible? was created by dbode
Hi,
according to the docs, the api seems to be always on www.mydomain.tld/api/v1
Is there any way to have the api available on e.g. api.mydomain.tld ?
A simple Alias in .htaccess doesn't seem to work here.
Any advices?
according to the docs, the api seems to be always on www.mydomain.tld/api/v1
Is there any way to have the api available on e.g. api.mydomain.tld ?
A simple Alias in .htaccess doesn't seem to work here.
Any advices?
Please Log in to join the conversation.
- steve.tsiopanos
- Offline
Less
More
- Posts: 163
7 years 7 months ago #101
by steve.tsiopanos
Replied by steve.tsiopanos on topic APi on own domain possible?
Right now that is not possible out of the box because the URL path is hard-coded to accommodate potential future future versioning.
/api/v1/
The issue with running it at the root domain level is that cAPI loads the Joomla application *through* the Slim application and the routing is completely independent of the Joomla router.
There is another option though. I think you could use a CNAME to mask www.mydomain.com.tld/api/v1 as api.mydomain.tld at the DNS zone level. I have not tried this yet but it should work (as long as I haven't hard-coded /api/v1 paths!).
We can follow-up in the support area if you need further assistance with such a solution.
/api/v1/
The issue with running it at the root domain level is that cAPI loads the Joomla application *through* the Slim application and the routing is completely independent of the Joomla router.
There is another option though. I think you could use a CNAME to mask www.mydomain.com.tld/api/v1 as api.mydomain.tld at the DNS zone level. I have not tried this yet but it should work (as long as I haven't hard-coded /api/v1 paths!).
We can follow-up in the support area if you need further assistance with such a solution.
Please Log in to join the conversation.