My spec won't parse

min

You added an integration and the first sync failed with a parse error, or a previously-working integration started failing. The vendor's OpenAPI document is malformed in some way. Sometimes we can work around it; sometimes we can't.

What we can recover from

These are common breakages we patch automatically:

Trailing junk after the document. Comments, console output, or a wrapper page accidentally served alongside the spec.
Mixed line endings. CRLF/LF inconsistency.
Encoding wobble. UTF-8 BOMs and Latin-1 mid-document.
Loose $ref resolution. Refs that point to a sibling file we can also fetch.
Mild OpenAPI 2.0 vs 3.x ambiguity. We auto-detect and parse with the right version.

If the document is mostly valid with one of these issues, you'll see a successful sync with no extra action.

What we can't recover from

These require the vendor to fix their document:

Genuinely invalid YAML/JSON. Mismatched braces, unclosed strings, malformed structure.
Missing info or paths blocks. OpenAPI without these isn't OpenAPI.
Circular $ref chains that don't resolve.
Specs split across hosts where we can't follow the refs (e.g. one ref points to an internal-only host).

When this happens, the integration shows Failed: parse error with the specific line and reason.

Steps to take

Open the spec URL in a browser. Does it return what you expect? Sometimes the URL silently became a redirect to a 404 page or a login screen.
Validate it locally. Run the spec through Swagger Editor or any OpenAPI validator. If it fails there too, it's a vendor problem.
Check for partial outages. Some vendors serve their spec from a CDN that occasionally serves stale or broken copies. Wait 15 minutes and force a sync.
Report it to the vendor. Most are responsive when you can point at a specific validation error. While you wait, Intello keeps the last known good snapshot — you don't lose history.

Library specs

If the failing integration came from the library, tell us. We maintain those specs and will either fix the source or switch to an alternative we host. You shouldn't have to deal with this for library integrations.