---
canonical: https://docs.jentic.com/guides/add-api-integration/
representation: markdown-alternate
# Canonical page: https://docs.jentic.com/guides/add-api-integration/
# This is the Markdown alternate of the page above.
title: "Add an API to Jentic Public APIs"
description: >-
  Request a new API integration for the Jentic Public APIs knowledge base by opening a
  GitHub issue with its OpenAPI Description to get it live in the catalog.
---

# Add API Integrations

Got an API you’d love to see in the [Jentic Public APIs](../reference/public-apis/overview.md) knowledge base?  
If you can point us to its **OpenAPI Description**, you’re only one GitHub issue away from having it live in the catalog that powers [API Search](../getting-started/api-search.md).

> **Important:** Please use the GitHub issue template named **“Import OpenAPI to Jentic Public APIs”** for all new API integration requests.  
> This template captures every detail our automation and reviewers need. While Discord is great for questions, **GitHub issues are the official intake channel** for new integrations.

---

## How to Request a New API Integration

1. **Open a New Issue on GitHub**
    * Navigate to the [Jentic Public APIs Issues page](https://github.com/jentic/jentic-public-apis/issues).
    * Click **“New issue”**.
    * Select the **“Import OpenAPI to Jentic Public APIs”** issue template.

2. **Complete the Issue Template**
    Provide:
    * **OpenAPI Descriptions URL** — direct raw link to the YAML/JSON file, or attach it.
    * **Vendor name** — e.g., `apisetu.gov.in/asrb`.
    * **Additional Information** (optional) — anything to help reviewers.

    **Example**
    ```text
    ## OpenAPI Description URL
    import_oas_url: https://api.apis.guru/v2/specs/apisetu.gov.in/asrb/3.0.0/openapi.json
    
    ## Vendor Name (Required)
    vendor_name: apisetu.gov.in/asrb
    ```

3. **Submit and Track**
    * Bots will label the issue automatically.
    * A maintainer reviews and verifies the spec.

4. **Import and Publication Process**
    * Spec is validated and placed in the [OAK Repository Structure](../reference/public-apis/oak-structure.md) (`apis/<provider>/<api>/<version>/openapi.json`).
    * CI runs lint/format checks; automated PRs may fix small issues.
    * Once merged, the API is searchable and runnable within Jentic.

---

## FAQ

**Do I need to understand Arazzo?**  
No — you describe workflows in plain English, and our tooling generates the Arazzo spec.

**What if I don't have an OpenAPI Description?**  
You can still open an issue. State that an OpenAPI isn’t available and link to the API’s docs. We may create one or help you generate it.

**Can I request APIs with complex auth (e.g., OAuth 2.0)?**  
Yes — ideally the OpenAPI Description defines security schemes. Include details in the template to ensure correct configuration.

---

## Additional Support

💬 [Discord](https://discord.gg/xRResx3ZNW) — community Q&A  
📂 [Public APIs – Overview](../reference/public-apis/overview.md)  
🗂 [OAK Repository Structure](../reference/public-apis/oak-structure.md)  

➡️ **Ready to add an API?**  
[Open the “Import OpenAPI to Jentic Public APIs” issue template](https://github.com/jentic/jentic-public-apis/issues/new?template=import_openapi.yml)