Unable to update custom schema using API | Community
Skip to main content
Indra-2
Community Advisor
Indra-2Community Advisor
Community Advisor
July 9, 2024
Solved

Unable to update custom schema using API

  • July 9, 2024
  • 1 reply
  • 1190 views
Request: 
 
[{
"op": "add",
"path": "/allOf/-",
"value": {
}
},
{
"op": "add",
"path": "/allOf/-",
"value": {
}
}
]
 
Respose:
 
{
"title": "Resource not found",
"status": 404,
"report": {
"registryRequestId": "fb25cbe5-cead-4fa9-8ec7-44a140e4e451",
"timestamp": "07-09-2024 03:08:20",
"detailed-message": "The requested schemas resource {{SCHEMA_ID}} with version 1.50.1 is not found."
},
"detail": "The requested schemas resource {{SCHEMA_ID}} with version 1.50.1 is not found."
}
Best answer by DavidRoss91

Yes, it is there in Params as well


@indra-2 it seems as if you are trying to use the {{schema_id}} as a variable. You need to remove it from the headers section and only have it defined within the params. If using as a variable, see the documentation here:
Store and reuse values using variables | Postman Learning Center

 

You can also try to manually add the schema id in the params with the actual value just to see if that works, prior to adding the variable.

1 reply

DavidRoss91
Community Advisor
DavidRoss91Community Advisor
Community Advisor
July 9, 2024

Hi @indra-2 

Are you inputting the Schema ID itself into the parameters of the PATCH request? The error message is referencing {{schema_id}} and not the specific Schema ID that you provided above. Could you provide some more context? Thanks!

 

https://developer.adobe.com/experience-platform-apis/references/schema-registry/#operation/patchSchema

 

David

    Indra-2
    Community Advisor
    Indra-2Community AdvisorAuthor
    Community Advisor
    July 9, 2024

    Hi David,

     

    I have defined in Header

      DavidRoss91
      Community Advisor
      DavidRoss91Community Advisor
      Community Advisor
      July 9, 2024

      Hi @indra-2 

      Ok so that is the problem. You need to add the schema ID into the parameters, and not the headers. Let me know if that works.

      David

        Terms & ConditionsAccessibility statement

        Loading footer...