/calendar/v2/event_instances

[sboutros]

Affected Product
Which product does this bug affect?
Calendar

Describe the bug
We pull events on an hourly basis and over the past 72 hours or so we see 3 sets of hourly calls to the event_instances endpoint where most of the data comes back as "null". I have reviewed issue #986 but this is different as 95% of the time the data is good. On the bad sessions, I see the first 8-10 events in the event_instances call return full data and then after that they all look like the json block below.

To Reproduce
Properly authenticaed requests to:
https://api.planningcenteronline.com/calendar/v2/event_instances?filter=future&include=resource_bookings,event_times,event&order=starts_at&per_page=99

Expected behavior
Good data in the response - as we receive 99% of the time.

Screenshots
{
"id": "xxx",
"name": null,
"approval_status": null,
"instance_id": "xxx",
"startz": "2025-12-14T16:00:00Z",
"endz": "2025-12-14T17:30:00Z",
"start": "2025-12-14 11:00",
"end": "2025-12-14 12:30",
"desc": null,
"occ_id": "200177249",
"summary": "https://api.planningcenteronline.com/calendar/v2/events/xxx",
"url": "https://chapel.churchcenter.com/calendar/event/xxx",
"resources": [
null,
null,
...
],
"resource_str": ",,,,,,,,,,,,,,,,,,,,,,,,,"
},

Additional Context:

• Endpoint: https://api.planningcenteronline.com/calendar/v2/event_instances?filter=future&include=resource_bookings,event_times,event&order=starts_at&per_page=99
• Language: php
• Authentication: OAuth 2

Additional context

I have..

• Reviewed the documentation found at https://developer.planning.center/docs
• Searched for previous issues reporting this bug
• Removed all private information from this issue (credentials, tokens, emails, phone numbers, etc.)
• Reviewed my issue for completeness

[tc4mpbell]

Hey @sboutros, thanks for writing in. 🤔

From the example JSON, it looks like you're translating/flattening the API response to a custom format -- can you give us an example of a "raw" API response[^1] that's returning this null data?

And it looks like you are getting back some attributes, like start/end?

---

[1]: i.e. in the original JSON-API format:

{
  "links": { ... },
  "data": [
    {
      "type": "EventInstance",
      "id": "...",
      "attributes": {...},
      "relationships": {
        "event": {...}
      },
    },
    ...
  ],
  "included": [...],
  "meta": {
    "total_count": 100,
    "count": 10
  }
}

[sboutros]

Am I able to send an entire json file without having to post it here?

[tc4mpbell]

You should be able to send it through our support contact form (https://www.planningcenter.com/support) -- just include a link to this issue and I'll make sure it gets routed to me.

[sboutros]

Hi Taylor, I've gone down a rabbit hole to review code on this side before putting any more work on your plate. One thing I did run into that I'm not having much luck with is adding the description attribute with the fields parameter to the event_instances endpoint I've tried several different ways to do it and not having any luck. Any advice - am I missing something? The call works and I get my 99 events but I am not able to get the description field for each event. This is the URL I am using: https://api.planningcenteronline.com/calendar/v2/event_instances?filter=future,approved&include=resource_bookings,event_times,event&order=starts_at&per_page=99&fields=description <https://developer.planning.center/docs/#/apps/calendar/2022-07-07/vertices/event_instance> Planning Center API Documentation<https://developer.planning.center/docs/#/apps/calendar/2022-07-07/vertices/event_instance> developer.planning.center<https://developer.planning.center/docs/#/apps/calendar/2022-07-07/vertices/event_instance> [apple-touch-icon.png]<https://developer.planning.center/docs/#/apps/calendar/2022-07-07/vertices/event_instance> On Dec 12, 2025, at 11:17 AM, Taylor Campbell ***@***.***> wrote: [https://avatars.githubusercontent.com/u/327601?s=20&v=4]tc4mpbell left a comment (planningcenter/developers#1394)<#1394 (comment)> You should be able to send it through our support contact form (https://www.planningcenter.com/support) -- just include a link to this issue and I'll make sure it gets routed to me. — Reply to this email directly, view it on GitHub<#1394 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANAZ5XPTAVKWQI2J42WLKL4BLTCPAVCNFSM6AAAAACO3Q6FEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBXGIZTINZUGM>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[tc4mpbell]

Hi @sboutros,

With fields, you'll also need to include the type of the record, like &fields[EventInstance]=description:

https://api.planningcenteronline.com/calendar/v2/event_instances?filter=future,approved&include=resource_bookings,event_times,event&order=starts_at&per_page=99&fields[EventInstance]=description

One other potentially helpful note:

• Once you're specifying fields[type]=, you'll only get back the fields you specifically request, so make sure to include everything you want in the list:

  fields[EventInstance]=starts_at,ends_at,description,...
  

Hope that helps!

[sboutros]

Hi Taylor, Thanks for the clarifications. I am calling event_instances endpoint (see $pco_url block at the bottom). When I call it without fields=[] I get a very rich response, 200+ lines of pretty printed json. If I include fields=[] and the list of fields as you advised I only get about 20 lines of json. Ultimately I am building the normalized json structure below but currently I need to make 3 API calls per calendar event - I am trying to reduce my PCO API calls. Any advice on how I can reduce API calls and still build the structure below? https://api.planningcenteronline.com/calendar/v2/event_instances?{params below} https://api.planningcenteronline.com/calendar/v2/events/{$e->relationships->event->data->id}<https://api.planningcenteronline.com/calendar/v2/events/%7B$e-%3Erelationships-%3Eevent-%3Edata-%3Eid%7D> https://api.planningcenteronline.com/calendar/v2/resource_bookings/{$res->id}<https://api.planningcenteronline.com/calendar/v2/resource_bookings/%7B$res-%3Eid%7D> { "id": "123", "name": "Trinity School Day", "approval_status": "A", "instance_id": “123", "startz": "2025-12-10T12:20:00Z", "endz": "2025-12-10T21:00:00Z", "start": "2025-12-10 07:20", "end": "2025-12-10 16:00", "desc": null, "occ_id": “456", "summary": "https:\/\/api.planningcenteronline.com\/calendar\/v2\/events\/123", "url": "https:\/\/xyzchapel.churchcenter.com\/calendar\/event\/123", "resources": [ "791744", "791745", "791746", "791747", "791762" ], "resource_str”: "791744,791745,791746,791747,791748,791762" }, $pco_url = "https://api.planningcenteronline.com/calendar/v2/event_instances?"; $pco_url .= "filter=future,approved&"; $pco_url .= "include=resource_bookings,event_times,event&"; $pco_url .= "order=starts_at&"; $pco_url .= "per_page=99&"; $pco_url .= "fields[EventInstance]=description,id,name,starts_at,ends_at,related,church_center_url,approval_status,event"; On Dec 15, 2025, at 8:32 AM, Taylor Campbell ***@***.***> wrote: [https://avatars.githubusercontent.com/u/327601?s=20&v=4]tc4mpbell left a comment (planningcenter/developers#1394)<#1394 (comment)> Hi @sboutros<https://github.com/sboutros>, With fields, you'll also need to include the type of the record, like &fields[EventInstance]=description: https://api.planningcenteronline.com/calendar/v2/event_instances?filter=future,approved&include=resource_bookings,event_times,event&order=starts_at&per_page=99&fields[EventInstance]=description One other potentially helpful note: * Once you're specifying fields[type]=, you'll only get back the fields you specifically request, so make sure to include everything you want in the list: fields[EventInstance]=starts_at,ends_at,description,... Hope that helps! — Reply to this email directly, view it on GitHub<#1394 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANAZ5WX3EP24R2A44KNUED4B2Z5NAVCNFSM6AAAAACO3Q6FEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNJVGY3TAOBRHA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[tc4mpbell]

Hi @sboutros,

Should be able to get that structure 🤔 -- here's how I'd imagine those would map to the JSON-API response (pseudocode):

    {
        "id": data[].id,
        "name": data[].attributes.name,
        "approval_status": included[]->Event.attributes.approval_status,
        "instance_id": data[].id,
        "startz": data[].attributes.starts_at,
        "endz": data[].attributes.ends_at,
        "start": data[].attributes.starts_at,
        "end": data[].attributes.ends_at,
        "desc": data[].attributes.description,
        "occ_id": ?,
        "summary": data[].relationships.event.links.related,
        "url": data[].attributes.church_center_url,
        "resources": included[]->ResourceBooking[].relationships.resource.id,
        "resource_str": included[]->ResourceBooking[].relationships.resource.id,
    },

That's with this URL (should be the same as the one you're generating above):

https://api.planningcenteronline.com/calendar/v2/event_instances?filter=future,approved&include=resource_bookings,event_times,event&order=starts_at&per_page=99&fields[EventInstance]=description,id,name,starts_at,ends_at,related,church_center_url,approval_status,event

Let me know what data you're not getting that you expect.

And just in case, make sure you're specifying the latest version with your API requests.

---

Example API response

{
  "links": {
    "self": "https://api.planningcenteronline.com/calendar/v2/event_instances?fields[EventInstance]=description%2Cid%2Cname%2Cstarts_at%2Cends_at%2Crelated%2Cchurch_center_url%2Capproval_status%2Cevent&filter=future%2Capproved&include=resource_bookings%2Cevent_times%2Cevent&order=starts_at&per_page=1",
    "next": "https://api.planningcenteronline.com/calendar/v2/event_instances?fields[EventInstance]=description%2Cid%2Cname%2Cstarts_at%2Cends_at%2Crelated%2Cchurch_center_url%2Capproval_status%2Cevent&filter=future%2Capproved&include=resource_bookings%2Cevent_times%2Cevent&offset=1&order=starts_at&per_page=1"
  },
  "data": [
    {
      "type": "EventInstance",
      "id": "333",
      "attributes": {
        "church_center_url": "https://[test account].churchcenter.com/calendar/event/333",
        "description": "<div>\n  <div>An afternoon of croquet.</div>\n</div>\n",
        "ends_at": "2025-12-18T14:30:00Z",
        "name": "🦆 Croquet party",
        "starts_at": "2025-12-18T12:30:00Z"
      },
      "relationships": {
        "event": {
          "links": {
            "related": "https://api.planningcenteronline.com/calendar/v2/events/999"
          },
          "data": {
            "type": "Event",
            "id": "999"
          }
        }
      },
      "links": {
        "self": "https://api.planningcenteronline.com/calendar/v2/event_instances/333"
      }
    }
  ],
  "included": [
    {
      "type": "ResourceBooking",
      "id": "444",
      "attributes": {
        "created_at": "2025-12-16T13:38:36Z",
        "ends_at": "2025-12-18T14:30:00Z",
        "quantity": 1,
        "starts_at": "2025-12-18T12:30:00Z",
        "updated_at": "2025-12-16T13:38:36Z"
      },
      "relationships": {
        "event": {
          "data": {
            "type": "Event",
            "id": "999"
          }
        },
        "event_instance": {
          "data": {
            "type": "EventInstance",
            "id": "333"
          }
        },
        "resource": {
          "data": {
            "type": "Resource",
            "id": "555"
          }
        }
      },
      "links": {
        "self": "https://api.planningcenteronline.com/calendar/v2/resource_bookings/444"
      }
    },
    {
      "type": "EventTime",
      "id": "ET-3-333",
      "attributes": {
        "ends_at": "2025-12-18T14:30:00Z",
        "name": "🦆 Croquet party",
        "starts_at": "2025-12-18T13:30:00Z",
        "visible_on_kiosks": true,
        "visible_on_widget_and_ical": true
      },
      "relationships": {
        "event": {
          "data": {
            "type": "Event",
            "id": "999"
          }
        }
      },
      "links": {}
    },
    {
      "type": "Event",
      "id": "999",
      "attributes": {
        "approval_status": "A",
        "archived_at": null,
        "created_at": "2025-11-06T13:20:19Z",
        "details": null,
        "image_url": null,
        "name": "🦆 Croquet party",
        "percent_approved": 100,
        "percent_rejected": 0,
        "updated_at": "2025-12-16T13:41:35Z",
        "visible_in_church_center": true
      },
      "relationships": {
        "calendar": {
          "data": {
            "type": "Calendar",
            "id": "default"
          }
        },
        "owner": {
          "data": {
            "type": "Person",
            "id": "888"
          }
        }
      },
      "links": {
        "self": "https://api.planningcenteronline.com/calendar/v2/events/999",
        "html": "https://calendar.planningcenteronline.com/events/999"
      }
    }
  ],
  "meta": {
    "total_count": 105,
    "count": 1,
    "next": {
      "offset": 1
    },
    "parent": {
      "id": "777",
      "type": "Organization"
    }
  }
}

[sboutros]

Taylor, As always, thank you for the thoughtful response I appreciate it. I was under the impression the API would use the latest version but I have updated our headers to include - "X-PCO-API-Version: 2022-07-07" In the existing code, we call this endpoint $rb = pcoAPIcall("https://api.planningcenteronline.com/calendar/v2/resource_bookings/{$res->id}", $authRow); and are looking for $rb->relationships->resource->data->id; In the call to event_instance below I get this result: If I eliminate the fields[EventsInstance] parameter I get the JSON block below it and I iterate over the 23 resource bookings to get the room IDs via the resource_bookings call above. Sorry for the complicated scenario - I am just trying to optimize our API calls (if possible) while maintaining our data model. Can you help me understand the impact of the fields parameter and how it changes the result set and also if you look at the RB json (3rd json block) I am ultimately trying to get (room) resource IDs along with the event details - so if there is a cleaner way to do so I am all ears. Thank you for sticking with me :-) WITH fields stdClass Object ( [type] => EventInstance [id] => 207083161 [attributes] => stdClass Object ( [church_center_url] => https://chapel.churchcenter.com/calendar/event/207083161 [description] => [ends_at] => 2025-12-17T21:00:00Z [name] => Trinity School Day [starts_at] => 2025-12-17T12:20:00Z ) [relationships] => stdClass Object ( [event] => stdClass Object ( [links] => stdClass Object ( [related] => https://api.planningcenteronline.com/calendar/v2/events/17914850 ) [data] => stdClass Object ( [type] => Event [id] => 17914850 ) ) ) [links] => stdClass Object ( [self] => https://api.planningcenteronline.com/calendar/v2/event_instances/207083161 ) ) WITHOUT fields stdClass Object ( [type] => EventInstance [id] => 207083161 [attributes] => stdClass Object ( [all_day_event] => [church_center_url] => https://chapel.churchcenter.com/calendar/event/207083161 [compact_recurrence_description] => Every Monday, Wednesday, and Friday [created_at] => 2025-12-03T13:58:11Z [ends_at] => 2025-12-17T21:00:00Z [location] => 123 [name] => Trinity School Day [published_ends_at] => 2025-12-17T21:00:00Z [published_starts_at] => 2025-12-17T12:30:00Z [recurrence] => Weekly [recurrence_description] => Every Monday, Wednesday, and Friday from 7:20am to 4:00pm beginning 12/05/2025 ending on 12/19/2025 [starts_at] => 2025-12-17T12:20:00Z [updated_at] => 2025-12-05T12:08:22Z ) [relationships] => stdClass Object ( [event] => stdClass Object ( [links] => stdClass Object ( [related] => https://api.planningcenteronline.com/calendar/v2/events/17914850 ) [data] => stdClass Object ( [type] => Event [id] => 17914850 ) ) [resource_bookings] => stdClass Object ( [links] => stdClass Object ( [related] => https://api.planningcenteronline.com/calendar/v2/event_instances/207083161/resource_bookings ) [data] => Array ( [0] => stdClass Object ( [type] => ResourceBooking [id] => 346910007 ) […23] => stdClass Object ) ) [event_times] => stdClass Object ( [links] => stdClass Object ( [related] => https://api.planningcenteronline.com/calendar/v2/event_instances/207083161/event_times ) [data] => Array ( [0] => stdClass Object ( [type] => EventTime [id] => ET-27971432-207083161 ) [1] => stdClass Object ( [type] => EventTime [id] => ET-27971433-207083161 ) ) ) ) [links] => stdClass Object ( [self] => https://api.planningcenteronline.com/calendar/v2/event_instances/207083161 ) ) ResourceBooking API call stdClass Object ( [type] => ResourceBooking [id] => 346910007 [attributes] => stdClass Object ( [created_at] => 2025-12-05T12:08:22Z [ends_at] => 2025-12-17T21:00:00Z [quantity] => 1 [starts_at] => 2025-12-17T12:20:00Z [updated_at] => 2025-12-05T12:08:22Z ) [relationships] => stdClass Object ( [event] => stdClass Object ( [data] => stdClass Object ( [type] => Event [id] => 17914850 ) ) [event_instance] => stdClass Object ( [data] => stdClass Object ( [type] => EventInstance [id] => 207083161 ) ) [resource] => stdClass Object ( [data] => stdClass Object ( [type] => Resource [id] => 791744 <<<— THIS IS WHAT WE NEED ) ) ) [links] => stdClass Object ………………….. ) On Dec 16, 2025, at 9:35 AM, Taylor Campbell ***@***.***> wrote: [https://avatars.githubusercontent.com/u/327601?s=20&v=4]tc4mpbell left a comment (planningcenter/developers#1394)<#1394 (comment)> Hi @sboutros<https://github.com/sboutros>, Should be able to get that structure 🤔 -- here's how I'd imagine those would map to the JSON-API response (pseudocode): { "id": data[].id, "name": data[].attributes.name, "approval_status": included[]->Event.attributes.approval_status, "instance_id": data[].id, "startz": data[].attributes.starts_at, "endz": data[].attributes.ends_at, "start": data[].attributes.starts_at, "end": data[].attributes.ends_at, "desc": data[].attributes.description, "occ_id": ?, "summary": data[].relationships.event.links.related, "url": data[].attributes.church_center_url, "resources": included[]->ResourceBooking[].relationships.resource.id, "resource_str": included[]->ResourceBooking[].relationships.resource.id, }, That's with this URL (should be the same as the one you're generating above): https://api.planningcenteronline.com/calendar/v2/event_instances?filter=future,approved&include=resource_bookings,event_times,event&order=starts_at&per_page=99&fields[EventInstance]=description,id,name,starts_at,ends_at,related,church_center_url,approval_status,event Let me know what data you're not getting that you expect. And just in case, make sure you're specifying the latest version<https://developer.planning.center/docs/#/overview/versioning> with your API requests.

…

________________________________ Example API response { "links": { "self": "https://api.planningcenteronline.com/calendar/v2/event_instances?fields[EventInstance]=description%2Cid%2Cname%2Cstarts_at%2Cends_at%2Crelated%2Cchurch_center_url%2Capproval_status%2Cevent&filter=future%2Capproved&include=resource_bookings%2Cevent_times%2Cevent&order=starts_at&per_page=1", "next": "https://api.planningcenteronline.com/calendar/v2/event_instances?fields[EventInstance]=description%2Cid%2Cname%2Cstarts_at%2Cends_at%2Crelated%2Cchurch_center_url%2Capproval_status%2Cevent&filter=future%2Capproved&include=resource_bookings%2Cevent_times%2Cevent&offset=1&order=starts_at&per_page=1" }, "data": [ { "type": "EventInstance", "id": "333", "attributes": { "church_center_url": "https://[test account].churchcenter.com/calendar/event/333", "description": "<div>\n <div>An afternoon of croquet.</div>\n</div>\n", "ends_at": "2025-12-18T14:30:00Z", "name": "🦆 Croquet party", "starts_at": "2025-12-18T12:30:00Z" }, "relationships": { "event": { "links": { "related": "https://api.planningcenteronline.com/calendar/v2/events/999" }, "data": { "type": "Event", "id": "999" } } }, "links": { "self": "https://api.planningcenteronline.com/calendar/v2/event_instances/333" } } ], "included": [ { "type": "ResourceBooking", "id": "444", "attributes": { "created_at": "2025-12-16T13:38:36Z", "ends_at": "2025-12-18T14:30:00Z", "quantity": 1, "starts_at": "2025-12-18T12:30:00Z", "updated_at": "2025-12-16T13:38:36Z" }, "relationships": { "event": { "data": { "type": "Event", "id": "999" } }, "event_instance": { "data": { "type": "EventInstance", "id": "333" } }, "resource": { "data": { "type": "Resource", "id": "555" } } }, "links": { "self": "https://api.planningcenteronline.com/calendar/v2/resource_bookings/444" } }, { "type": "EventTime", "id": "ET-3-333", "attributes": { "ends_at": "2025-12-18T14:30:00Z", "name": "🦆 Croquet party", "starts_at": "2025-12-18T13:30:00Z", "visible_on_kiosks": true, "visible_on_widget_and_ical": true }, "relationships": { "event": { "data": { "type": "Event", "id": "999" } } }, "links": {} }, { "type": "Event", "id": "999", "attributes": { "approval_status": "A", "archived_at": null, "created_at": "2025-11-06T13:20:19Z", "details": null, "image_url": null, "name": "🦆 Croquet party", "percent_approved": 100, "percent_rejected": 0, "updated_at": "2025-12-16T13:41:35Z", "visible_in_church_center": true }, "relationships": { "calendar": { "data": { "type": "Calendar", "id": "default" } }, "owner": { "data": { "type": "Person", "id": "888" } } }, "links": { "self": "https://api.planningcenteronline.com/calendar/v2/events/999", "html": "https://calendar.planningcenteronline.com/events/999" } } ], "meta": { "total_count": 105, "count": 1, "next": { "offset": 1 }, "parent": { "id": "777", "type": "Organization" } } } — Reply to this email directly, view it on GitHub<#1394 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANAZ5X4SMCBKVP5QZWTJYD4CAKDLAVCNFSM6AAAAACO3Q6FEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNRQHA3TEMRQGM>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[tc4mpbell]

Hmm, I think the info you want is in the included section of the JSON response; looking at those examples, your code may be just looking at the data section.

I.e., given a (pseudocode) API call like:

response = pcoApi(`calendar/v2/event_instances?include...`)

the instance-specific data comes back in the data array:

eventInstances = response.data

but the extra included records come back in an additional top-level included key:

includedRecords = response.included

So for example, the (truncated) response looks like this:

{
  "data": [
    {
      "type": "EventInstance",
      "id": "333",
      "attributes": ...,
      "relationships": ...
    }
    ...
  ],
  "included": [
    {
      "type": "ResourceBooking",
      "id": "444",
      "attributes": ...
      },
      "relationships": {
        "event_instance": {
          "data": {
            "type": "EventInstance",
            "id": "333"
          }
        },
        "resource": {
          "data": {
            "type": "Resource",
            "id": "555"
          }
        }
      }
    }
  ]
}

So given an instance (data.eventInstances[0] => #333), you'd look through data.included to find the ResourceBooking records that have a relationship to EventInstance#333, and from that you'll have the associated Resource ID as well.

Hope that makes sense, let me know if not!

---

One other difference I noticed from your examples:

• When using fields, if you want to get the included resource_bookings and event_times back in your EventInstance relationships collection, you can add those to the fields as well:

  &fields[EventInstance]=...,event,event_times,resource_bookings
  

[sboutros]

Sorry still scratching my head here - I do not see a top-level included section - am I missing something? $pco_url = "https://api.planningcenteronline.com/calendar/v2/event_instances?"; $pco_url .= "filter=future,approved&"; $pco_url .= "include=resource_bookings,event_times,event&"; $pco_url .= "order=starts_at&"; $pco_url .= "per_page=99&"; $pco_url .= "fields[EventInstance]=description,id,name,starts_at,ends_at,related,church_center_url,approval_status,event,event_times,resource_bookings,resource"; On Dec 16, 2025, at 1:48 PM, Taylor Campbell ***@***.***> wrote: [https://avatars.githubusercontent.com/u/327601?s=20&v=4]tc4mpbell left a comment (planningcenter/developers#1394)<#1394 (comment)> Hmm, I think the info you want is in the included section of the JSON response; looking at those examples, your code may be just looking at the data section. I.e., given a (pseudocode) API call like: response = pcoApi(`calendar/v2/event_instances?include...`) the instance-specific data comes back in the data array: eventInstances = response.data but the extra included records come back in an additional top-level included key: includedRecords = response.included So for example, the (truncated) response looks like this: { "data": [ { "type": "EventInstance", "id": "333", "attributes": ..., "relationships": ... } ... ], "included": [ { "type": "ResourceBooking", "id": "444", "attributes": ... }, "relationships": { "event_instance": { "data": { "type": "EventInstance", "id": "333" } }, "resource": { "data": { "type": "Resource", "id": "555" } } } } ] } So given an instance (data.eventInstances[0] => #333), you'd look through data.included to find the ResourceBooking records that have a relationship to EventInstance#333, and from that you'll have the associated Resource ID as well. Hope that makes sense, let me know if not!

…

________________________________ One other difference I noticed from your examples: * When using fields, if you want to get the included resource_bookings and event_times back in your EventInstance relationships collection, you can add those to the fields as well: &fields[EventInstance]=...,event,event_times,resource_bookings — Reply to this email directly, view it on GitHub<#1394 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANAZ5WB5C7W3Z3OVT5MWS34CBHZJAVCNFSM6AAAAACO3Q6FEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNRRHEZDIMJRGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[tc4mpbell]

The JSON response should come back with these top-level keys:

{
   links: {...}
   data: [...]
   included: [...]
   meta: {...}
}

You should be able to hit the URL in a browser (if you're logged in to an org) and verify that's what you see as well.

If you see the included section in that raw/browser response, but don't see it when you're making the call programmatically, I'd guess something in your API client code is discarding or ignoring it somehow. Let me know what you find!