Forbidden when creating a background check

[annettevillacrusis]

Related Product Which product is this question related to? People

Describe the question Issuing a POST to https://api.planningcenteronline.com/people/v2/people/{id}/background_checks

{
     "data": 
        {
            "type": "BackgroundCheck",
            "attributes": {
                "result": "clear"
            }
        }
}

gives me this result

{
    "errors": [
        {
            "status": "403",
            "title": "Forbidden",
            "detail": "You do not have access to this resource",
            "meta": {
                "description": "User with id {userid} cannot create a BackgroundCheck."
            }
        }
    ]
}

What have you tried that worked? It was working up until 6 March 2024 using the same credentials. I confirmed that the user is still allowed to create background checks using the UI.

What have you tried that didn't work? Added the user as a background check administrator despite being an organization admin. Tried it on different PCO accounts.

Additional context I am using the Personal Access Token of an organization admin.

I have..

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

[seven1m]

Thank you for the report! We are working to resolve this now...

[zanebliss]

@annettevillacrusis we have pushed up a fix for this. Can you please try again and let us know if you have any issues?

[annettevillacrusis]

@ZaneBliss It's all good now. It's working again. Thanks for the quick resolution!

[seven1m]

@annettevillacrusis I wanted to let you know that we have added a new attribute to this endpoint called status that accepts a wider range of values. You can read about the attribute in the docs.

Our plan is to remove the result attribute from this endpoint in the very near future, possibly in the next few weeks. Please migrate any existing code to start using the status attributes and not the result attribute as soon as possible.

Please note that the version of the API you are using is still in Beta and we may have further adjustments to make in the future.

[annettevillacrusis]

@annettevillacrusis I wanted to let you know that we have added a new attribute to this endpoint called status that accepts a wider range of values. You can read about the attribute in the docs.

Our plan is to remove the result attribute from this endpoint in the very near future, possibly in the next few weeks. Please migrate any existing code to start using the status attributes and not the result attribute as soon as possible.

Please note that the version of the API you are using is still in Beta and we may have further adjustments to make in the future.

@seven1m I appreciate you letting me know about this change. I have migrated our code.

[seven1m]

Thank you! That was fast.