custom connector error

Question

While creating the custom connector below is the error I'm receiving.

Bad request : 400

{ "type": "https://libertyglobal--tst2.custhelp.com/services/rest/connect/exceptions/OSC-CREST-00025", "title": "Bad Request", "status": 400, "detail": "Illegal/malformed id '@incident_ID'", "instance": "https://libertyglobal--tst2.custhelp.com/services/rest/connect/v1.4/incidents/@incident_ID", "o:errorCode": "OSC-CREST-00025" }

My details in connector below:

URL: https://libertyglobal--tst2.custhelp.com/services/rest/connect/v1.4/incidents/@incident_ID

Message Body:

{ <br>    "threads": { <br>        "entryType": { <br>            "id": 1 <br>        }, <br>        "text": "This is an append 2" <br>    } <br>}

Request Type: Patch

Header:

OSvC-CREST-Application-Context = This is a valid request for account.

Answer 1

Hi Anindita Kar,

Welcome to Microsoft Community.

Based on the original description, we understand that your device encountered problems related to custom connectors and Oracle product.

The 400 Bad Request error with the code OSC-CREST-00025 indicates that the request could not be understood by the server. The error message suggests that there is an illegal or malformed ID in your request URL.

Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.

REST API for Oracle B2C Service - Error Codes![](https://learn-attachment.microsoft.com/api/attachments/85e4e372-b8d6-4501-b2ff-f84c0a97c9bc?platform=QnA"https://docs.oracle.com/en/cloud/saas/b2c-service/cxsvc/c_osvc_status_codes.html" title="docs.oracle.com" rel="ugc nofollow">REST API for Oracle B2C Service - Status Codes

According to Oracle's related support article, here are a few things you may need to check:

• You may need to ensure that the "@incident_ID" in your URL is correctly formatted and valid. It should be a proper identifier without any special characters or spaces. Make sure the URL is correctly formed and does not contain any typos or incorrect segments.
• Ensure that all required headers are correctly set. The OSvC-CREST-Application-Context header seems to be correctly included, but double-check its value and length (it should not exceed 40 characters).
• Verify that the JSON payload in the message body is correctly formatted and valid. It looks correct, but it's always good to double-check.

The URL should look something like this:

https://libertyglobal--tst2.custhelp.com/services/rest/connect/v1.4/incidents/{incident_ID}

Replace {incident_ID} with the actual ID of the incident you are trying to update.

Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.

REST API for Oracle B2C Service - Get an incident

If you have verified all these aspects and are still facing issues, you might want to consult the Oracle B2C Service REST API documentation for more detailed information on error codes and troubleshooting steps.

Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.

REST API for Oracle B2C Service - About the REST APIs

If the "Custom connectors" you are referring to are services related to Microsoft Power Automate, you can try consulting a more experienced community for technical guidance specific to the Microsoft Power Automate service.

Custom connectors overview | Microsoft Learn

Custom connector frequently asked questions for Azure Logic Apps, Power Automate, and Power Apps | Microsoft Learn

Thanks for your patience and understanding.

Best Regards,

Kyo.Y - MSFT | Microsoft Community Technical Support