Import Your API
Bring your API into Theneo from a spec file, a public URL, a Postman collection, or your codebase. This page covers each method, when to use it, and where to find the details, without repeating what already lives in the API reference and CLI sections.
Ways to import
Theneo fits both product managers importing by hand and developers automating the whole thing. Pick the path that matches your workflow.
Upload a file or URL
Create or edit a project, then upload an OpenAPI, Swagger, WSDL, or GraphQL file, or paste a public spec URL.
Postman collection
Connect your Postman API key and pull a collection straight into your project.
Theneo CLI
Run theneo import to bring a spec in from the command line, scriptable and repeatable.
Git and CI/CD
Sync from GitHub, GitLab, or Bitbucket so docs update when your repo changes.
Which should I use?
- A one-time or occasional import: Upload a file or paste a spec URL in the editor.
- Your team works in Postman: Import a Postman collection, or set up Postman Sync to keep it current.
- You want automation or version control: Use the Theneo CLI.
- Docs must track every code change: Connect GitHub, GitLab, or Bitbucket sync.
- You don't have a spec yet: Define your API by hand in the editor.
No spec to start from? You can build your API endpoint by endpoint in the editor. See Manually defining an API, the next section.
Where to go next
On this page
- Import Your API