# REST custom urls

**URL:** <https://discuss.emberjs.com/t/rest-custom-urls/4344>\
**Category:** Ember Data\
**Created:** [March 2, 2014, 4:35pm UTC](https://discuss.emberjs.com/t/rest-custom-urls/4344 "2014-03-02T16:35:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RuslanZavacky](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/ruslanzavacky/32/15542_2.png) [@RuslanZavacky](https://discuss.emberjs.com/u/RuslanZavacky)\
**Post date:** [March 2, 2014, 4:35pm UTC](https://discuss.emberjs.com/t/rest-custom-urls/4344/1 "2014-03-02T16:35:40Z")

</div>

I can’t find a good example of working fully with REST, every example touches only CRUD. REST allows urls as /api/1/reports/general.

How to properly send request to API for nested url?

I’ve tried:

```auto
this.store.find('report/general')
this.store.find('report.general')

```

Last idea was to use just `this.store.find('report', { type: 'some-type' })`. But this also not gone well, I have different model for reports/general.

I’ll appreciate any help, thanks!

UPDATE:

One idea that actually worked, to use native jQuery `Ember.$.getJSON`:

```auto
model: function () {
    return Ember.RSVP.hash({
      indicator: this.store.find('indicator'),
      profile: this.store.find('profile'),
      conversationUpdate: Ember.$.getJSON('api/1/reports/conversation.json')
    });
  },

```

Is there any better solution for this?

---

<div class="post-metadata">

**Author:** ![kimroen](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/kimroen/32/15491_2.png) [@kimroen](https://discuss.emberjs.com/u/kimroen)\
**Post date:** [March 12, 2014, 5:10pm UTC](https://discuss.emberjs.com/t/rest-custom-urls/4344/2 "2014-03-12T17:10:14Z")

</div>

It doesn’t look like Ember Data supports nested REST resources at the moment. There’s been some discussions around it and a few proposed solutions, but nothing that’s actually shipped as of now (that I know of).

[This issue on the Ember Data repo](https://github.com/emberjs/data/issues/186) discussed it, and the last reply from Yehuda states (6 months ago) that “I’ll keep it in mind going forward.”

[This discussion](http://discuss.emberjs.com/t/i-was-being-silly-to-fight-ember-data-on-nested-urls-i-think/2082) on these forums also goes through some reasons why nested resources might not be the best solution anyway, as well as possible solutions.

You could probably find some temporary solution by overriding [`buildUrl`](http://emberjs.com/api/data/classes/DS.RESTAdapter.html#method_buildURL) in your adapters.