jbarrieault
commented
1 year ago Hey @jgreiman!
While we can't speak to the abilities of third-party APIs, our Services API does include endpoints for creating as well as reading Blockouts, which may be useful to you for this project.
Some relevant documentation:
- Blockout: used for creating & updating blockouts, with supports for recurring blockout schedule patterns.
- BlockoutDate used for reading individual dates that have been blocked out.
That should be a good starting point for an creating your integration as far as the Services side goes. If you are looking for some more inspiration on how to implement this or other Planning Center API related projects, consider checking out the #api channel of our Community Slack.
Best of luck!
We have what I suspect is a problem others have run into. Most of the church uses CCB (Church Community Builder) to handle setting their blockout dates for scheduling. This includes much of the kids ministry. The worship team uses PCO. Several volunteers (including my wife) serve in both areas and thus needs to put in the same blockout dates for both programs. I couldn't find an export or import in PCO, so there's no native integration. Both products offer an API, so it seems straightforward enough to write something to read from one API and write to the other. Any recommendations on which direction it should go?