Adding funding source to master account

API Support
1

Hi,

I’m following the instructions here to find out the funding account of my master account.

I’m sending the following:

http GET https://api-sandbox.dwolla.com/accounts/ad5f2162-404a-4c4c-994e-6ab6c3a13254 \
Content-Type:application/vnd.dwolla.v1.hal+json \
Accept:application/vnd.dwolla.v1.hal+json \
Authorization:"Bearer xxx"

And I get the following:

{
    "_links": {
        "self": {
            "href": "https://api-sandbox.dwolla.com/accounts/ad5f2162-404a-4c4c-994e-6ab6c3a13254",
            "resource-type": "account",
            "type": "application/vnd.dwolla.v1.hal+json"
        }
    },
    "id": "ad5f2162-404a-4c4c-994e-6ab6c3a13254",
    "name": "xxx"
}

But according to the document I’m suppose to be seeing a “funding-sources” section. How do I add this? I don’t see an option in my sandbox dashboard.

2

Hi @gavnewalkar,

Thanks for posting the full req/res bodies! You’d have to change the endpoint you’re calling to the following

GET https://api-sandbox.dwolla.com/accounts/ad5f2162-404a-4c4c-994e-6ab6c3a13254/funding-sources

That should give you back a list of all funding-sources attached to your Master Account. Please let me know if you have any questions!

3

Hi sherya,

I’ve tried what you suggested but I’m now getting an error.

http GET https://api-sandbox.dwolla.com/accounts/ad5f2162-404a-4c4c-994e- 
6ab6c3a13254/funding-sources?removed=false \
Content-Type:application/vnd.dwolla.v1.hal+json \
Accept:application/vnd.dwolla.v1.hal+json \
Authorization:"Bearer xxx"

Response HTTP/1.1 401 Unauthorized:

{
    "code": "InvalidScope",
    "message": "Missing or invalid scopes for requested endpoint."
}
4

Hi @gavnewalkar, you’d have to replace the Account id ad5f2162-404a-4c4c-994e-6ab6c3a13254 with your Master Account’s ID.

Here’s a request that you can run to retrieve your Account ID via the API,

GET https://api-sandbox.dwolla.com/
Accept: application/vnd.dwolla.v1.hal+json
Authorization: Bearer xxxxxxxxxxxxxxxxxxxxxxxxx

5

Hi @shreya,

Thanks that worked.

It might just be me but that step was not obvious in the documentation. Please point this out to your developers :slight_smile:

6

Noted! Thanks, @gavnewalkar!