planningcenter / developers

Planning Center API docs and support

Home Page:https://developer.planning.center/docs/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Several APIs are not working

ClifDunaway opened this issue · comments

I use the APIs to pull data for First Baptist church, Simpsonville, SC. Recently, I discuvered that the APIs are now showing a 404 error message.

Here is one example:

https://api.planningcenteronline.com/check-ins/v2/check_ins/1/event_period

Here is what is returned:

{"errors":[{"status":"404","title":"Not Found","detail":"The resource you requested could not be found"}]}

Affected Product
Which product does this bug affect?

Describe the bug

To Reproduce

Expected behavior

Screenshots

Additional Context:

  • Endpoint: [e.g. API endpoint I'm using]
  • Language: [e.g. Programming language I'm using]
  • Authentication: [e.g. OAuth 2, Personal Access Token, Browser Session (Cookie)]

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

When you are attempting to access specific resources, if that resource does not exist in your organization, it is expected behavior that you would get a 404 error.

It looks like in the URLs that you are attempting to access, you are trying to access check-ins and events with an id of 1, which I am guessing is not actually a check-in or event in your org.

You might want to try to access https://api.planningcenteronline.com/check-ins/v2/check_ins or https://api.planningcenteronline.com/check-ins/v2/events/ to see the list of valid check-ins and events and then you can use the ids from those to access your data about the specific resources with the urls like you have above with the valid ids substituted in.

Those are examples that do not contain real world data. The explorer might give you a better feel for how this works with real data.

It seems like this is resolved. Let us know if you have any more questions or concerns.