Missing data in the response data

[drkdelaney]

Related Product
Which product is this question related to?
Calendar

Describe the question
I'm trying to use the endpoint: calendar/v2/tags/{tagId}/events to get all of the events with that tag id. When I use it, it is missing data in the attributes from the response body.

What have you tried that worked?
When I use the API explorer (https://api.planningcenteronline.com/explorer/calendar/v2/tags/{tagId}/events)the data returns what I expect.

What have you tried that didn't work?
When I use a javascript fetch with my API token to that endpoint the response is missing data.

Additional context
Here is a calendar attribute from the explore:

"approval_status":"A"
"created_at":"2022-05-17T05:17:15Z"
"description":NULL
"image_url":NULL
"name":"test"
"percent_approved":100
"percent_rejected":0
"registration_url":"https://########.churchcenter.com/registrations/events/{id}"
"summary":NULL
"updated_at":"2022-05-17T05:17:35Z"
"visible_in_church_center":false

These are the properties in my fetch attribute response:

approval_status: 'A',
      archived_at: '2022-05-17T08:06:02Z',
      created_at: '2022-05-17T05:17:15Z',
      details: null,
      image_url: null,
      name: 'test',
      percent_approved: 100,
      percent_rejected: 0,
      updated_at: '2022-05-17T05:17:35Z',
      visible_in_church_center: false

I have..

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

[nicholaskillin]

@derekedelaney Thanks for reaching out to let us know that you are getting different attributes in your
API calls than you are seeing in the API explorer.

The API explorer always uses the latest version of our APIs. You can see the API version being used by the explorer here:

Based on the attributes that you are getting back, it looks like you are using an outdated version of our API and will need to specify the newest version to get back the attributes you are expecting.

You can learn more about versioning, including how to specify a version, in our documentation.
https://developer.planning.center/docs/#/overview/versioning

Hope that helps! Let us know if we can assist with anything else.

[drkdelaney]

@nicholaskillin thanks for the reply. The link to versioning was really helpful. I was able to get the correct data with the second option listed in the article.

There are 2 ways to specify a version:
1. Setting a per-app default here
2. Passing a header on every request: X-PCO-API-Version with a value of YYYY-MM-DD

As far as the first option, this is what my defaults look like under my personal access token that was using:

My assumption was it would be using the version from that list. I'll continue using the header value but wanted to also point out the difference with the image.

[nicholaskillin]

@derekedelaney Thanks for letting us know about that! This looks like a bug that slipped under the radar a while back. It also looks like this bug only affects the Calendar API. All other products are respecting the default version selected.

We are working towards a fix on this, but for now keeping the version in your request header should get around the bug.

[nicholaskillin]

@derekedelaney Just wanted to follow up here to let you know that we have fixed this issue. Now your Calendar API calls should respect the default version you configure in API without needing to specify the version in the header of your requests.