Schemas are not updated after uploading file using curl

[xwojazeg (rumcajs)]

Hello Team, I’d like to report that after sending file using API my schema is not updated (it should have new description). Output after sending the request as follows:

{"data":{"counters":{"endpointCreated":0,"endpointUpdated":0,"endpointIgnored":0,"endpointFailed":0,"endpointFolderCreated":0,"endpointFolderUpdated":0,"endpointFolderIgnored":0,"endpointFolderFailed":0,"schemaCreated":0,"schemaUpdated":0,"schemaIgnored":0,"schemaFailed":0,"schemaFolderCreated":0,"schemaFolderUpdated":0,"schemaFolderIgnored":0,"schemaFolderFailed":0,"securitySchemeCreated":0,"securitySchemeUpdated":0,"securitySchemeIgnored":0,"securitySchemeFailed":0,"securitySchemeFolderCreated":0,"securitySchemeFolderUpdated":0,"securitySchemeFolderIgnored":0,"securitySchemeFolderFailed":0}}}

When I use the website everything’s correct as it should be. What can I do to have the same result using API?
I also use values stored in json file as follows:

  "options": {
    "targetEndpointFolderId": 0,
    "targetSchemaFolderId": 0,
    "endpointOverwriteBehavior": "OVERWRITE_EXISTING",
    "schemaOverwriteBehavior": "OVERWRITE_EXISTING",
    "updateFolderOfChangedEndpoint": false,
    "prependBasePath": false
  }

[Apidog Support]

It might be related to the input field content you’re using for the API import. Could you share the input field value (after removing sensitive information) or provide a minimal sample of your input data so we can investigate?

[xwojazeg (rumcajs)]

Of course! Here’s the json that I’m attaching in curl request. Normally it’s much bigger, but that’s one of schemas that isn’t updated after the successful request is done. Moreover, I’ve attached a screenshot which contains that specified model in Apidog. Descriptions are empty.

[Apidog Support]

It seems the KrsRdfRecordModel referenced in your file doesn’t exist, which would prevent the description from being imported. However, when the referenced model is properly included, the description should import correctly as shown in my screenshot.

Since your screenshot indicates the description still didn’t import even with the referenced model present (which I couldn’t reproduce), could you please share a more complete version of your import file for further investigation?

[xwojazeg (rumcajs)]

It does exist, when I’m importing the exactly same file using UI descriptions are set as it should be. What else should I attach to import file for you to reproduce the problem?

[Apidog Support]

The import file should include all referenced data schemas. Based on my tests, descriptions are correctly set when importing through the open api. If you can still reproduce the issue, please share the complete file with us for further investigation.

[xwojazeg (rumcajs)]

Ok, I’m attaching full json file which I’m including into the request (request.json). In that file you can find KrsRdfRecordModel schema, it contains identifiers section, where I left “APIDOG I’M HERE - I’M NOT IMPORTED INTO DOCUMENTATION VIA API” description. When I use API it’s not updating schema in Apidog , but when I use update via GUI it’s updated as it should be. Please help me with my issue and let me know if you found some solution

[Apidog Support]

Hello, I’ve tested importing your data through the OpenAPI interface and it seems to be working correctly. I noticed in your file that the “input” field is of object type, but according to our documentation, it should be a string type. Please verify your import format - if your data is in JSON format, you need to escape it as a string before importing. Try this approach and let me know if it resolves the issue.

[xwojazeg (rumcajs)]

Hello, I’ve tested different way to store docs as a string (as you mentioned before) and its working. Thank you very much for your help!