How to create a jsonpath to instagram business account in a batch request with the Graph API?

Question

My goal is to create a batch request with dependent calls as documented here: https://developers.facebook.com/docs/graph-api/making-multiple-requests#operations

You can reference the results of a previous operation using JSONPath in form post parameters in addition to query string parameters. I can't get the right JSONPath to make it work when there are multiple elements in the data array that have an instagram_business_account.id (iba_id)

The two calls that I want to make are /me/accounts?fields=instagram_business_account /17841400714813297?fields=business_discovery.username(thomasguntenaar){media_count} my batch looks like

[
{"method":"GET","name":"get-ig", "relative_url":"me/accounts?fields=instagram_business_account"},
{"method":"GET", "relative_url":"{result=get-ig:$.data..instagram_business_account.id}?fields=business_discovery.username(thomasguntenaar){media_count}}"}
]

in the second query you are supposed to put the JSONPath to the instagram business account id after result= I get this error back

 {
    "code": 404,
    "body": "{
   \"error\": {
      \"message\": \"(#803) Some of the aliases you requested do not exist: 17841400714813297,17841403388404550,17841401383243593\",
      \"type\": \"OAuthException\",
      \"code\": 803,
      \"fbtrace_id\": \"FV8qA+oA7fp\"
   }
}"
  }

Facebooks json response after the first call is

{
  "data": [
    {
      "id": "466912700123917"
    },
    {
      "id": "502655553273897"
    },
    {
      "instagram_business_account": {
        "id": "17841400714813297"
      },
      "id": "503124266815195"
    },
    {
      "instagram_business_account": {
        "id": "17841403388404550"
      },
      "id": "510613645695833"
    },
    {
      "instagram_business_account": {
        "id": "17841401383243593"
      },
      "id": "2061834074114937"
    }
  ],
  "paging": {
    "cursors": {
      "before": "NDY2OTEyNzAwMTIzOTE3",
      "after": "MjA2MTgzNDA3NDExNDkzNwZDZD"
    }
  }
}

When you query the second request like this ?ids=17841400714813297,17841403388404550,17841401383243593&fields=business_discovery.username(thomasguntenaar){username,media_count} the response looks like this

{
  "17841400714813297": {
    "business_discovery": {
      "username": "thomasguntenaar",
      "media_count": 76,
      "id": "17841400714813297"
    },
    "id": "17841400714813297"
  },
  "17841403388404550": {
    "business_discovery": {
      "username": "thomasguntenaar",
      "media_count": 76,
      "id": "17841400714813297"
    },
    "id": "17841403388404550"
  },
  "17841401383243593": {
    "business_discovery": {
      "username": "thomasguntenaar",
      "media_count": 76,
      "id": "17841400714813297"
    },
    "id": "17841401383243593"
  }
}

Answer 1

(#803) Some of the aliases you requested do not exist: 17841400714813297,17841403388404550,17841401383243593

Apparently the API thinks this was supposed to be one id, and doesn’t realize it is supposed to be three separate ones.

The API has a syntax to request data for more than one object in one request - instead of /{id}?fields=foo, you can make a request of the form ?ids={1,2,3}&fields=foo, to request this data for the objects with ids 1, 2 and 3 in one go. The resulting data structure will contain a sub-structure for each of those ids.

The same structure should work in batch requests as well, when parts (here, the IG account ids returned by the previous query) are dynamically inserted.