3828893 - How do I solve User Provisioning v4 API Errors?

The User Provisioning Service v4 API may return multiple types of errors during user creation or update.

These errors can be reviewed by retrieving a Detailed Provisioning Request Status, which includes information about each individual extension processed during the request.

When a POST, PUT, or PATCH operation results in a failure, the API generates a provisionId. This identifier can be used to request the detailed status, which contains:

• the extension where the error occurred
• the field that produced the error
• the error code and message
• the schemaPath, which identifies the exact field in the payload

Below is an example of an error returned in the detailed provisioning status:

{
                    "name": "urn:ietf:params:scim:schemas:extension:spend:2.0:User",
                    "status": {
                        "completed": true,
                        "success": false,
                        "code": "500",
                        "result": "error"
                    },
                    "messages": [
                        {
                            "code": "INVALID_VALUE",
                            "message": "Invalid List Item",
                            "schemaPath": "urn:ietf:params:scim:schemas:extension:spend:2.0:User:customData[id eq \"custom21\"].value",
                            "type": "error"
                        }
                    ]
                }

This article explains how to analyze and resolve common User Provisioning Service (UPS) v4 API errors by reviewing the provisioning status and understanding the error information returned from the API. , KBA , CON-INT , Integrations , Problem