successful-api-specification-import
Overview
This rule belongs to the apimatic-process-validation
ruleset and states that:
An input API specification can fail to import if it contains validation issues (e.g. input files may not be valid against standard formats) or if the import process ran into internal issues. You can attempt to fix the file using given suggestions and troubleshooting tips below or contact APIMatic team for more details.
Property | Value |
---|---|
Enabled | Yes |
Maximum Severity | Blocking |
Message | Provided API specification failed to import. |
Code | APIMATICPROCESS_V002 |
Type | Validation |
Rule System | Semantic |
Broad Category | Processes |
Tags | process apimatic semantic validation import api specification |
Suggested Fixes
- Resolve any specification related errors/warnings to proceed further.
- Ensure that your file uses valid JSON/YAML/XML.
- Ensure that the file does not contain any circular references.
- Ensure that any required properties are not missing.
- Visit the official standard documentation of the format, that your file uses, to determine the root cause of the issue.
- Avoid using any special/forbidden characters in your files.
- Ensure that your file does not have any unexpected nulls.
- Ensure that all files are in one of the supported formats only.
- Make sure that the file contents are complete.
- Contact APIMatic team for more details if you think the API specification is valid and still failing to import.