Centralized Resources plan

some page.hbs

{{!
{
    "resources": {
        "photos": "photos",
        "photos-profile": "photos-profile",
        "other": "http://other-api.com/data.json"
    }
}
}}

url filter.json

{
    "resources": {
        "photos": "http://www.photos-api.com/user/12345/photos/",
        "photos-profile": "http://www.photos-api.com/user/12345/",
        "thing": {
            "url": "http://www.thing-api.com/user/12345/thing/",
            "headers": {
                "key": "12345"
            }
        }
    },
    "defaults": {
        "http://www.photos-api.com/*": {
            "headers": {
                "key": "12345"
            }
        }
    }
}

And how do dynamic segments work?

Dynamic segments should work here the same way you'd expect them to normally. If you define a dynamic segment in the URL it will attempt to use dynamic data to fill in the blanks when it's used on a page.

So if I define this in the resources.json:

{
    "resources": {
        "photo": "http://www.photos-api.com/user/12345/photos/{id}"
    }
}

And I use it in page.hbs:

{{!
{
    "resources": {
        "photo": "photo"
    }
}
}}

If I go to /page?id=5 I'll be fetching http://www.photos-api.com/user/12345/photos/5.