@nangohq/providers 0.71.4 → 0.71.6

package/providers.yaml

@@ -814,6 +814,61 @@ affinity-v2:
             example: 'nrlW2KR5m-qUCA-rTqKb_EUK1swERlenqn70KNMMrTM'
             doc_section: '#step-1-generating-your-api-key'
 
+agencyzoom:
+    display_name: AgencyZoom
+    categories:
+        - crm
+    auth_mode: TWO_STEP
+    body_format: json
+    token_url: https://api.agencyzoom.com/v1/api/auth/login
+    token_params:
+        username: ${credentials.username}
+        password: ${credentials.password}
+    token_headers:
+        content-type: application/json
+        accept: application/json
+    token_response:
+        token: jwt
+    proxy:
+        base_url: https://api.agencyzoom.com
+    docs: https://nango.dev/docs/api-integrations/agencyzoom
+    docs_connect: https://nango.dev/docs/api-integrations/agencyzoom/connect
+    credentials:
+        username:
+            type: string
+            title: Username
+            description: Your AgencyZoom account email address.
+            doc_section: '#step-1-obtain-your-credentials'
+        password:
+            type: string
+            title: Password
+            description: Your AgencyZoom account password.
+            secret: true
+            doc_section: '#step-1-obtain-your-credentials'
+
+agentline:
+    display_name: AgentLine
+    categories:
+        - communication
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://api.agentline.cloud
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /v1/agents
+    docs: https://nango.dev/docs/api-integrations/agentline
+    docs_connect: https://nango.dev/docs/api-integrations/agentline/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: Your AgentLine API key.
+            pattern: '^al_live_[a-zA-Z0-9_]+$'
+            doc_section: '#step-1-finding-your-api-key'
+
 agiloft:
     display_name: Agiloft
     categories:
@@ -1976,6 +2031,53 @@ atlassian:
         base_url: https://api.atlassian.com
     docs: https://nango.dev/docs/integrations/all/atlassian
 
+athenahealth:
+    display_name: athenahealth
+    categories:
+        - other
+    auth_mode: OAUTH2_CC
+    token_url: https://${connectionConfig.subdomain}.platform.athenahealth.com/oauth2/v1/token
+    token_request_auth_method: basic
+    token_params:
+        grant_type: client_credentials
+    scope_separator: ' '
+    proxy:
+        base_url: https://${connectionConfig.subdomain}.platform.athenahealth.com
+        connection_config:
+            practiceId: ${connectionConfig.practiceId}
+    docs: https://nango.dev/docs/api-integrations/athenahealth
+    docs_connect: https://nango.dev/docs/api-integrations/athenahealth/connect
+    connection_config:
+        subdomain:
+            type: string
+            title: API Environment
+            description: The athenahealth environment to connect to.
+            enum:
+                - api
+                - api.preview
+            doc_section: '#step-2-choose-your-environment'
+            order: 1
+        practiceId:
+            type: string
+            title: Practice ID
+            description: The ID of your athenahealth practice.
+            pattern: '^[0-9]+$'
+            example: '195900'
+            doc_section: '#step-3-find-your-practice-id'
+            order: 2
+    credentials:
+        client_id:
+            type: string
+            title: Client ID
+            description: The client ID for your registered athenahealth app.
+            doc_section: '#step-4-connect-your-athenahealth-account'
+        client_secret:
+            type: string
+            title: Client Secret
+            description: The client secret for your registered athenahealth app.
+            secret: true
+            doc_section: '#step-4-connect-your-athenahealth-account'
+
 atlassian-admin:
     display_name: Atlassian Cloud Admin
     categories:
@@ -2305,13 +2407,10 @@ auvik:
         region:
             type: string
             title: Region
-            description: The region of your Auvik account (visible in your browser address bar when logging into the Auvik web UI).
+            description: The region of your Auvik account (visible in your browser address bar when logging into the Auvik web UI), e.g. us1, us2, eu1, lnx.
             doc_section: '#step-2-determine-your-region'
-            enum:
-                - us1
-                - us2
-                - us6
-                - eu1
+            example: us1
+            pattern: '^[a-z0-9-]+$'
     docs: https://nango.dev/docs/integrations/all/auvik
     docs_connect: https://nango.dev/docs/integrations/all/auvik/connect
 
@@ -4321,6 +4420,38 @@ canva-scim:
             description: The API key for your Canva scim account
             doc_section: '#step-1-finding-canva-api-key'
 
+cdw:
+    display_name: CDW
+    categories:
+        - erp
+        - e-commerce
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://${connectionConfig.baseUrl}
+        headers:
+            subscription-key: ${apiKey}
+    docs: https://nango.dev/docs/api-integrations/cdw
+    docs_connect: https://nango.dev/docs/api-integrations/cdw/connect
+    credentials_verification_script: cdwCredentialsVerification
+    connection_config:
+        baseUrl:
+            type: string
+            title: Environment
+            description: The CDW API gateway you want to connect to.
+            enum:
+                - apiconnect.cdw.com/b2b
+                - apiconnect.preprod.cdw.com/pprd/b2b
+            order: 1
+            doc_section: '#step-3-choosing-your-base-url'
+    credentials:
+        apiKey:
+            type: string
+            title: Subscription Key
+            description: The subscription key from your CDW API Management developer portal account.
+            example: a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4
+            pattern: '^[a-fA-F0-9]{32}$'
+            doc_section: '#step-2-subscribing-to-a-product-and-generating-a-subscription-key'
+
 cerby:
     display_name: Cerby
     categories:
@@ -4444,6 +4575,38 @@ chargebee:
             default_value: ''
             hidden: true
 
+chartboost:
+    display_name: Chartboost
+    categories:
+        - marketing
+        - gaming
+    auth_mode: OAUTH2_CC
+    body_format: json
+    token_url: https://api.chartboost.com/v5/oauth/token
+    token_params:
+        grant_type: client_credentials
+        audience: https://public.api.gateway.chartboost.com
+    proxy:
+        base_url: https://api.chartboost.com
+    docs: https://nango.dev/docs/api-integrations/chartboost
+    docs_connect: https://nango.dev/docs/api-integrations/chartboost/connect
+    credentials:
+        client_id:
+            type: string
+            title: Client ID
+            description: Your Chartboost API client_id.
+            example: a3f8c1d9b2e47a5c6f0b8d1e3a9c2f
+            pattern: '^[a-f0-9]+$'
+            doc_section: '#step-1-obtain-your-api-credentials'
+        client_secret:
+            type: string
+            title: Client Secret
+            description: Your Chartboost API client_secret.
+            example: a1b2c3d4e5f6********************************************9c8d7e6f
+            pattern: '^[a-f0-9]+$'
+            secret: true
+            doc_section: '#step-1-obtain-your-api-credentials'
+
 chatarmin:
     display_name: Chatarmin
     categories:
@@ -4637,6 +4800,50 @@ checkout-com-sandbox:
     docs: https://nango.dev/docs/integrations/all/checkout-com-sandbox
     docs_connect: https://nango.dev/docs/integrations/all/checkout-com-sandbox/connect
 
+chili-piper:
+    display_name: Chili Piper
+    categories:
+        - crm
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://fire.chilipiper.com/api/fire-edge
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /v1/org/health/ping
+    docs: https://nango.dev/docs/api-integrations/chili-piper
+    docs_connect: https://nango.dev/docs/api-integrations/chili-piper/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: The API Access Token generated from your Chili Piper account.
+            doc_section: '#step-1-generating-your-api-key'
+
+chili-piper-mcp:
+    display_name: Chili Piper (MCP)
+    categories:
+        - crm
+        - mcp
+    auth_mode: MCP_OAUTH2
+    client_registration: dynamic
+    authorization_url: https://fire.chilipiper.com/api/fire-edge/v1/oauth/authorize
+    token_url: https://fire.chilipiper.com/api/fire-edge/v1/oauth/token
+    registration_url: https://fire.chilipiper.com/api/fire-edge/v1/oauth/register
+    authorization_params:
+        response_type: code
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://fire.chilipiper.com/api/fire-edge/v1/org/mcp
+        headers:
+            accept: application/json,text/event-stream
+    docs: https://nango.dev/docs/api-integrations/chili-piper-mcp
+
 chorus:
     display_name: Chorus
     categories:
@@ -7537,6 +7744,84 @@ epc-gov-uk:
             example: 'a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2'
             doc_section: '#step-2-finding-your-api-key'
 
+epic:
+    display_name: Epic (FHIR)
+    categories:
+        - other
+    auth_mode: TWO_STEP
+    body_format: form
+    token_url: https://${connectionConfig.interconnectUrl}/oauth2/token
+    token_params:
+        grant_type: client_credentials
+        client_assertion_type: urn:ietf:params:oauth:client-assertion-type:jwt-bearer
+        client_assertion: ${credentials.assertion}
+        scope: ${credentials.scope}
+    token_headers:
+        content-type: application/x-www-form-urlencoded
+        accept: application/json
+    assertion:
+        type: jwt
+        singleUse: true
+        key: ${credentials.privateKey}
+        lifetimeInSeconds: 300
+        header:
+            alg: ES256
+            kid: ${credentials.keyId}
+        payload:
+            iss: ${credentials.clientId}
+            sub: ${credentials.clientId}
+            aud: https://${connectionConfig.interconnectUrl}/oauth2/token
+            jti: ${random}
+    token_response:
+        token: access_token
+        token_expiration: expires_in
+        token_expiration_strategy: expireIn
+    proxy:
+        base_url: https://${connectionConfig.interconnectUrl}/api
+        headers:
+            accept: application/fhir+json
+    docs: https://nango.dev/docs/api-integrations/epic
+    setup_guide_url: https://nango.dev/docs/api-integrations/epic/how-to-register-your-own-epic-app
+    docs_connect: https://nango.dev/docs/api-integrations/epic/connect
+    integration_config:
+        clientId:
+            type: string
+            title: Client ID
+            description: Your registered application's Client ID.
+            order: 1
+        keyId:
+            type: string
+            title: Key ID
+            description: The kid of the EC (P-256) key registered in your hosted JWKS file.
+            order: 2
+        privateKey:
+            type: string
+            title: Private Key
+            description: The EC (P-256) private key (PEM) matching your published JWKS public key. Signed with ES256.
+            secret: true
+            order: 3
+        scope:
+            type: string
+            title: Scope
+            description: The SMART Backend Services scope(s) granted to this Client ID.
+            order: 4
+    credentials:
+        assertion:
+            type: string
+            title: ''
+            description: ''
+            automated: true
+    connection_config:
+        interconnectUrl:
+            type: string
+            prefix: https://
+            suffix: /oauth2/token
+            title: Interconnect Server URL
+            description: This health system's Epic Interconnect Server URL.
+            example: fhir.epic.com/interconnect-fhir-oauth
+            doc_section: '#step-1-finding-your-interconnect-server-url'
+            order: 1
+
 epic-games:
     display_name: Epic Games
     categories:
@@ -7549,6 +7834,26 @@ epic-games:
         base_url: https://api.epicgames.dev
     docs: https://nango.dev/docs/integrations/all/epic-games
 
+epost-klara:
+    display_name: ePost (KLARA)
+    categories:
+        - other
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://api.klara.ch
+        headers:
+            x-api-key: ${apiKey}
+    docs: https://nango.dev/docs/api-integrations/epost-klara
+    docs_connect: https://nango.dev/docs/api-integrations/epost-klara/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: Your KLARA API key.
+            format: uuid
+            example: 0b6df221-****-****-****-********e06d
+            doc_section: '#step-1-finding-your-api-key'
+
 ergo:
     display_name: Ergo
     categories:
@@ -7783,7 +8088,7 @@ expensify:
     docs_connect: https://nango.dev/docs/integrations/all/expensify/connect
 
 factorial:
-    display_name: Factorial
+    display_name: Factorial (OAuth)
     categories:
         - hr
     auth_mode: OAUTH2
@@ -7794,6 +8099,41 @@ factorial:
         base_url: https://api.factorialhr.com/api
     docs: https://nango.dev/docs/integrations/all/factorial
 
+factorial-api-key:
+    display_name: Factorial (API Key)
+    categories:
+        - hr
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://${connectionConfig.domain}/api || https://api.factorialhr.com/api
+        headers:
+            x-api-key: ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /2026-07-01/resources/api_public/credentials
+    docs: https://nango.dev/docs/api-integrations/factorial-api-key
+    docs_connect: https://nango.dev/docs/api-integrations/factorial-api-key/connect
+    connection_config:
+        domain:
+            type: string
+            title: Environment
+            description: The Factorial API environment to connect to.
+            order: 1
+            format: hostname
+            enum:
+                - api.factorialhr.com
+                - api.eu2.demo.factorial.dev
+            doc_section: '#step-2-choosing-your-environment'
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: The API Key generated from your Factorial account
+            example: 'eyJraWQiOiJmYWN.******************************.*****************************'
+            pattern: '^[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+$'
+            doc_section: '#step-1-generating-your-api-key'
+
 fairing:
     display_name: Fairing
     categories:
@@ -8199,6 +8539,32 @@ findymail:
             title: API Key
             description: The API key for your FindyMail account
 
+finta:
+    display_name: Finta
+    categories:
+        - banking
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://api.finta.io/
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            headers:
+                content-type: application/json
+            endpoints:
+                - /v2/me
+    docs: https://nango.dev/docs/api-integrations/finta
+    docs_connect: https://nango.dev/docs/api-integrations/finta/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: The API key for your Finta account.
+            pattern: '^finta_[A-Za-z0-9]+$'
+            example: finta_ZdzcJWJv********************fVsY
+            doc_section: '#step-1-finding-your-api-key'
+
 firefish:
     display_name: Firefish
     scope_separator: ' '
@@ -8790,10 +9156,28 @@ garmin:
         base_url: https://apis.garmin.com
     docs: https://nango.dev/docs/integrations/all/garmin
 
-gebruder-weiss:
-    display_name: Gebrüder Weiss
+garmin-oauth2:
+    display_name: Garmin (OAuth2)
     categories:
-        - erp
+        - sports
+    auth_mode: OAUTH2
+    authorization_url: https://connect.garmin.com/oauth2Confirm
+    token_url: https://diauth.garmin.com/di-oauth2-service/oauth/token
+    authorization_params:
+        response_type: code
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://apis.garmin.com
+    docs: https://nango.dev/docs/api-integrations/garmin-oauth2
+    setup_guide_url: https://nango.dev/docs/api-integrations/garmin-oauth2/how-to-register-your-own-garmin-oauth2-api-oauth-app
+
+gebruder-weiss:
+    display_name: Gebrüder Weiss
+    categories:
+        - erp
     auth_mode: OAUTH2_CC
     authorization_url: https://my.api.gw-world.com/authorize
     token_url: https://my.api.gw-world.com/token
@@ -9258,6 +9642,51 @@ gitlab-pat:
             doc_section: '#step-1-finding-your-hostname'
             order: 1
 
+gitlab-group-token:
+    alias: gitlab
+    display_name: GitLab (Group Access Token)
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://${connectionConfig.hostname}
+        headers:
+            private-token: ${apiKey}
+        retry:
+            at:
+                - 'x-ratelimit-reset'
+        verification:
+            method: GET
+            headers:
+                content-type: application/json
+            endpoints:
+                - /api/v4/user
+    docs: https://nango.dev/docs/api-integrations/gitlab-group-token
+    docs_connect: https://nango.dev/docs/api-integrations/gitlab-group-token/connect
+    credentials:
+        apiKey:
+            type: string
+            title: Group Access Token
+            example: glpat-PMJoma_*******.***.***xwve
+            pattern: '^glpat-[A-Za-z0-9._-]+$'
+            description: The Group Access Token issued for your GitLab group.
+            doc_section: '#step-3-create-a-group-access-token'
+    connection_config:
+        hostname:
+            type: string
+            title: Hostname
+            description: The hostname of your GitLab instance
+            format: hostname
+            example: gitlab.com
+            doc_section: '#step-1-find-your-hostname'
+            order: 1
+        groupId:
+            type: string
+            title: Group ID
+            description: The numeric ID of the GitLab group this token belongs to.
+            example: '12345678'
+            pattern: '^[0-9]+$'
+            doc_section: '#step-2-find-your-group-id'
+            order: 2
+
 ghost-admin:
     display_name: Ghost (Admin API)
     categories:
@@ -10043,6 +10472,42 @@ grain-api-key:
             title: API Key
             description: The personal access token to your Grain account
 
+greenfield-meditech:
+    display_name: MEDITECH Greenfield
+    categories:
+        - other
+    auth_mode: OAUTH2
+    authorization_url: https://${connectionConfig.authHost}/oauth/authorize
+    token_url: https://${connectionConfig.host}/oauth/token
+    authorization_params:
+        response_type: code
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://${connectionConfig.host}
+    docs: https://nango.dev/docs/api-integrations/greenfield-meditech
+    docs_connect: https://nango.dev/docs/api-integrations/greenfield-meditech/connect
+    setup_guide_url: https://nango.dev/docs/api-integrations/greenfield-meditech/how-to-register-your-own-greenfield-meditech-api-oauth-app
+    connection_config:
+        authHost:
+            type: string
+            title: Authorization host
+            description: The MEDITECH host that issues authorization codes.
+            example: greenfield-apis.meditech.com
+            format: hostname
+            prefix: https://
+            order: 1
+        host:
+            type: string
+            title: FHIR API host
+            description: The MEDITECH host that issues tokens and serves the FHIR API.
+            example: greenfield-prod-apis.meditech.com
+            format: hostname
+            prefix: https://
+            order: 2
+
 greenhouse:
     display_name: Greenhouse (OAuth)
     categories:
@@ -10454,6 +10919,62 @@ hackerrank-work:
             default_value: ''
             hidden: true
 
+hail:
+    display_name: Hail
+    categories:
+        - communication
+        - dev-tools
+        - marketing
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://api.hail.so
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /calls
+    docs: https://nango.dev/docs/api-integrations/hail
+    docs_connect: https://nango.dev/docs/api-integrations/hail/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: Your Hail account API key.
+            pattern: '^hl_live_[A-Za-z0-9_-]+$'
+            example: hl_live_************
+            doc_section: '#step-1-getting-your-api-key'
+
+hail-mcp:
+    display_name: Hail (MCP)
+    categories:
+        - communication
+        - dev-tools
+        - marketing
+        - mcp
+    auth_mode: MCP_OAUTH2
+    client_registration: dynamic
+    authorization_url: https://hail.so/api/auth/oauth2/authorize
+    token_url: https://hail.so/api/auth/oauth2/token
+    registration_url: https://hail.so/api/auth/oauth2/register
+    default_scopes:
+        - offline_access
+    registration_params:
+        grant_types:
+            - authorization_code
+            - refresh_token
+        response_types:
+            - code
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://mcp.hail.so
+        headers:
+            accept: application/json,text/event-stream
+    docs: https://nango.dev/docs/api-integrations/hail-mcp
+
 haileyhr:
     display_name: Hailey HR
     categories:
@@ -10688,6 +11209,25 @@ hibob-service-user:
     docs: https://nango.dev/docs/integrations/all/hibob-service-user
     docs_connect: https://nango.dev/docs/integrations/all/hibob-service-user/connect
 
+hibob-oauth:
+    display_name: HiBob (OAuth)
+    categories:
+        - hr
+    auth_mode: OAUTH2
+    authorization_url: https://auth.app.hibob.com/oauth2/v1/apps/authorize
+    token_url: https://auth.app.hibob.com/oauth2/v1/apps/token
+    token_request_auth_method: basic
+    authorization_params:
+        response_type: code
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    scope_separator: ' '
+    proxy:
+        base_url: https://api.hibob.com
+    docs: https://nango.dev/docs/api-integrations/hibob-oauth
+
 heygen:
     display_name: HeyGen
     categories:
@@ -11149,7 +11689,7 @@ instagram:
         - social
     auth_mode: OAUTH2
     scope_separator: ','
-    authorization_url: https://api.instagram.com/oauth/authorize
+    authorization_url: https://www.instagram.com/oauth/authorize
     token_url: https://api.instagram.com/oauth/access_token
     refresh_url: https://graph.instagram.com/refresh_access_token
     proxy:
@@ -12758,6 +13298,31 @@ linkhut:
         base_url: https://api.ln.ht
     docs: https://nango.dev/docs/integrations/all/linkhut
 
+livetennisapi:
+    display_name: Live Tennis API
+    categories:
+        - sports
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://api.livetennisapi.com
+        headers:
+            x-api-key: ${apiKey}
+            accept: application/json
+        verification:
+            method: GET
+            endpoints:
+                - /api/public/v1/matches
+    docs: https://nango.dev/docs/api-integrations/livetennisapi
+    docs_connect: https://nango.dev/docs/api-integrations/livetennisapi/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: The API key for your Live Tennis API account. It starts with `twjp_`.
+            example: twjp_xxxxxxxxxxxxxxxxxxxx
+            pattern: '^twjp_\S+$'
+            doc_section: '#step-1-generating-your-api-key'
+
 lokalise:
     display_name: Lokalise
     categories:
@@ -13006,6 +13571,35 @@ luma:
             title: API Key
             description: The API key for your Luma account
 
+luma-v2:
+    display_name: Luma (v2)
+    categories:
+        - productivity
+        - ticketing
+    auth_mode: API_KEY
+    proxy:
+        headers:
+            x-luma-api-key: ${apiKey}
+        base_url: https://public-api.luma.com
+        retry:
+            after:
+                - 'retry-after'
+        verification:
+            method: GET
+            headers:
+                content-type: application/json
+            endpoints:
+                - /v1/users/get-self
+    docs: https://nango.dev/docs/api-integrations/luma-v2
+    docs_connect: https://nango.dev/docs/api-integrations/luma-v2/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: The API key for your Luma account
+            pattern: '^secret-[a-zA-Z0-9]+$'
+            example: secret-a1B2c3D4e5F6g7H8i9J0k1L2m
+
 lumos:
     display_name: Lumos
     categories:
@@ -13449,6 +14043,35 @@ medallia:
             default_value: ''
             hidden: true # deprecating this in favor of apiHostUrl
 
+meilisearch:
+    display_name: Meilisearch
+    categories:
+        - search
+    auth_mode: API_KEY
+    proxy:
+        base_url: ${connectionConfig.instanceUrl}
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /version
+    connection_config:
+        instanceUrl:
+            type: string
+            title: Instance URL
+            description: The base URL of your Meilisearch instance.
+            example: https://ms-1a2b3c4d5e6f.meilisearch.io
+            pattern: '^https?://.+[^/]$'
+            order: 1
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: A Meilisearch API key (not the master key).
+    docs: https://nango.dev/docs/api-integrations/meilisearch
+    docs_connect: https://nango.dev/docs/api-integrations/meilisearch/connect
+
 metabase:
     display_name: Metabase
     categories:
@@ -13533,6 +14156,24 @@ meta-marketing-api:
     docs: https://nango.dev/docs/api-integrations/meta-marketing-api
     setup_guide_url: https://nango.dev/docs/api-integrations/meta-marketing-api/how-to-register-your-own-meta-marketing-api-oauth-app
 
+meta-mcp:
+    display_name: Meta Ads (MCP)
+    categories:
+        - marketing
+        - mcp
+    auth_mode: OAUTH2
+    scope_separator: ','
+    authorization_url: https://www.facebook.com/v26.0/dialog/oauth
+    token_url: https://graph.facebook.com/v26.0/oauth/access_token
+    authorization_params:
+        response_type: code
+    proxy:
+        base_url: https://mcp.facebook.com
+        headers:
+            accept: application/json,text/event-stream
+    docs: https://nango.dev/docs/api-integrations/meta-mcp
+    setup_guide_url: https://nango.dev/docs/api-integrations/meta-mcp/how-to-register-your-own-meta-mcp-oauth-app
+
 microsoft:
     display_name: Microsoft
     auth_mode: OAUTH2
@@ -14750,6 +15391,30 @@ namely-pat:
             description: The Personal Access Token for your Namely account
             doc_section: '#step-2-generating-your-personal-access-token'
 
+neon:
+    display_name: Neon
+    categories:
+        - dev-tools
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://console.neon.tech/api
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /v2/users/me
+    docs: https://nango.dev/docs/api-integrations/neon
+    docs_connect: https://nango.dev/docs/api-integrations/neon/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: Your Neon API key.
+            pattern: '^(napi_)?[a-z0-9]{64}$'
+            example: napi_1a2b3c4d5e6f****************************************************
+            doc_section: '#step-1-creating-an-api-key'
+
 nerdio:
     display_name: Nerdio
     categories:
@@ -15089,8 +15754,8 @@ ninjaone-saas-backup:
             type: string
             title: API Host
             description: The host from your NinjaOne SaaS Backup API URL.
-            example: dropsuite.us
-            pattern: '^(dropsuite\.com|dropsuite\.(us|uk|ca)|dropsuite-au\.com|[a-z0-9.-]+\.dropsuite\.com)$'
+            example: na-saas-npp.backup.ninjarmm.com
+            pattern: '^([a-z0-9]([a-z0-9-]*[a-z0-9])?\.backup\.ninjarmm\.com|dropsuite\.com|dropsuite\.(us|uk|ca)|dropsuite-au\.com|[a-z0-9.-]+\.dropsuite\.com)$'
             prefix: https://
             suffix: /api
             order: 1
@@ -15147,6 +15812,54 @@ nocrm:
             order: 1
             doc_section: '#step-1-finding-your-subdomain'
 
+nooks:
+    display_name: Nooks (OAuth)
+    categories:
+        - marketing
+    auth_mode: OAUTH2
+    authorization_url: https://oauth.nooks.in/oauth/authorize
+    token_url: https://oauth.nooks.in/oauth/token
+    authorization_params:
+        response_type: code
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://partner-api.nooks.in
+        retry:
+            after:
+                - 'retry-after'
+    docs: https://nango.dev/docs/api-integrations/nooks
+    setup_guide_url: https://nango.dev/docs/api-integrations/nooks/how-to-register-your-own-nooks-api-oauth-app
+
+nooks-api-key:
+    display_name: Nooks (API Key)
+    categories:
+        - marketing
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://partner-api.nooks.in
+        headers:
+            authorization: Bearer ${apiKey}
+        retry:
+            after:
+                - 'retry-after'
+        verification:
+            method: GET
+            endpoints:
+                - /v1/users?page[size]=1
+    docs: https://nango.dev/docs/api-integrations/nooks-api-key
+    docs_connect: https://nango.dev/docs/api-integrations/nooks-api-key/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: The API key for your Nooks workspace.
+            pattern: '^nooks-api-'
+            example: nooks-api-********************************
+            doc_section: '#step-1-generate-an-api-key'
+
 northbeam:
     display_name: Northbeam
     categories:
@@ -15482,28 +16195,66 @@ okta:
             suffix: .okta.com
             prefix: https://
 
-okta-cc:
-    display_name: Okta (Client Credentials)
+okta-api-key:
+    display_name: Okta (API Token)
     categories:
         - dev-tools
         - iam
-    auth_mode: OAUTH2_CC
-    token_url: https://${connectionConfig.hostname}/oauth2/v1/token || https://${connectionConfig.subdomain}.okta.com/oauth2/v1/token
-    token_request_auth_method: private_key_jwt
-    token_params:
-        grant_type: client_credentials
+    auth_mode: API_KEY
     proxy:
-        base_url: https://${connectionConfig.hostname} || https://${connectionConfig.subdomain}.okta.com
+        base_url: https://${connectionConfig.hostname}
+        headers:
+            authorization: SSWS ${apiKey}
         retry:
             at:
                 - 'x-rate-limit-reset'
-        paginate:
-            type: 'link'
-            limit_name_in_request: 'limit'
-            link_rel_in_response_header: 'next'
-    docs: https://nango.dev/docs/api-integrations/okta-cc
-    docs_connect: https://nango.dev/docs/api-integrations/okta-cc/connect
-    credentials:
+        verification:
+            method: GET
+            endpoints:
+                - /api/v1/users/me
+    docs: https://nango.dev/docs/api-integrations/okta-api-key
+    docs_connect: https://nango.dev/docs/api-integrations/okta-api-key/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Token
+            description: The API token generated from your Okta org.
+            pattern: '^00[A-Za-z0-9_-]{40}$'
+            example: 00qJ-P************************************
+            doc_section: '#step-1-generating-your-api-token'
+    connection_config:
+        hostname:
+            type: string
+            title: Okta Domain
+            description: The full hostname of your Okta account.
+            format: hostname
+            prefix: https://
+            example: dev-12345678.okta.com
+            order: 1
+            doc_section: '#step-2-finding-your-okta-domain'
+
+okta-cc:
+    display_name: Okta (Client Credentials)
+    categories:
+        - dev-tools
+        - iam
+    auth_mode: OAUTH2_CC
+    token_url: https://${connectionConfig.hostname}/oauth2/v1/token || https://${connectionConfig.subdomain}.okta.com/oauth2/v1/token
+    token_request_auth_method: private_key_jwt
+    token_params:
+        grant_type: client_credentials
+    proxy:
+        base_url: https://${connectionConfig.hostname} || https://${connectionConfig.subdomain}.okta.com
+        retry:
+            at:
+                - 'x-rate-limit-reset'
+        paginate:
+            type: 'link'
+            limit_name_in_request: 'limit'
+            link_rel_in_response_header: 'next'
+    docs: https://nango.dev/docs/api-integrations/okta-cc
+    docs_connect: https://nango.dev/docs/api-integrations/okta-cc/connect
+    credentials:
         client_id:
             type: string
             title: Client ID
@@ -15575,6 +16326,41 @@ onlogist:
             description: The API key for your OnLogist account
             doc_section: '#step-1-finding-your-api-key'
 
+omni:
+    display_name: Omni Analytics
+    categories:
+        - analytics
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://${connectionConfig.subdomain}.omniapp.co/api
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            headers:
+                content-type: application/json
+            endpoints:
+                - /v1/whoami
+    docs: https://nango.dev/docs/api-integrations/omni
+    docs_connect: https://nango.dev/docs/api-integrations/omni/connect
+    connection_config:
+        subdomain:
+            type: string
+            title: Instance Subdomain
+            description: Your Omni instance subdomain.
+            order: 1
+            pattern: '^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$'
+            example: acme
+            doc_section: '#step-1-finding-your-instance-subdomain'
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: An Omni Organization API key or Personal Access Token (PAT).
+            pattern: '^omni_[a-z]+_[A-Za-z0-9]+$'
+            example: omni_osk_40S5****************************************Aakd
+            doc_section: '#step-2-creating-an-api-key'
+
 one-drive:
     display_name: OneDrive for Business
     categories:
@@ -17223,6 +18009,42 @@ pushpay-chms-v1:
             secret: true
             doc_section: '#step-2-create-an-api-user'
 
+pushpay-chms-v2:
+    display_name: Pushpay ChMS (v2)
+    categories:
+        - crm
+        - productivity
+    auth_mode: OAUTH2
+    authorization_url: https://oauth.ccbchurch.com/oauth/authorize
+    token_url: https://api.ccbchurch.com/oauth/token
+    body_format: json
+    disable_pkce: true
+    scope_separator: ' '
+    authorization_params:
+        response_type: code
+        subdomain: ${connectionConfig.subdomain}
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://api.ccbchurch.com
+        headers:
+            accept: application/vnd.ccbchurch.v2+json
+    docs: https://nango.dev/docs/api-integrations/pushpay-chms-v2
+    docs_connect: https://nango.dev/docs/api-integrations/pushpay-chms-v2/connect
+    setup_guide_url: https://nango.dev/docs/api-integrations/pushpay-chms-v2/how-to-register-your-own-pushpay-chms-v2-oauth-app
+    connection_config:
+        subdomain:
+            type: string
+            title: Church subdomain
+            description: The subdomain for the Pushpay ChMS (Church Community Builder) site to authorize.
+            example: yourchurch
+            pattern: '^[a-zA-Z0-9-]+$'
+            prefix: https://
+            suffix: .ccbchurch.com
+            doc_section: '#step-1-finding-your-church-subdomain'
+
 plain:
     display_name: Plain
     categories:
@@ -18689,6 +19511,41 @@ revivn:
             secret: true
             doc_section: '#step-1-get-your-oauth2-credentials'
 
+revolut-business:
+    display_name: Revolut Business
+    categories:
+        - banking
+    auth_mode: OAUTH2
+    authorization_url: https://${connectionConfig.authorizeHost}/app-confirm
+    authorization_params:
+        response_type: code
+    disable_pkce: true
+    token_url: https://${connectionConfig.apiHost}/api/1.0/auth/token
+    refresh_url: https://${connectionConfig.apiHost}/api/1.0/auth/token
+    scope_separator: ','
+    proxy:
+        base_url: https://${connectionConfig.apiHost}
+    docs: https://nango.dev/docs/api-integrations/revolut-business
+    docs_connect: https://nango.dev/docs/api-integrations/revolut-business/connect
+    setup_guide_url: https://nango.dev/docs/api-integrations/revolut-business/how-to-register-your-own-revolut-business-api-oauth-app
+    connection_config:
+        authorizeHost:
+            type: string
+            title: Authorization Host
+            description: The Revolut Business authorization hostname for your environment.
+            enum:
+                - business.revolut.com
+                - sandbox-business.revolut.com
+            doc_section: '#step-1-selecting-your-environment'
+        apiHost:
+            type: string
+            title: API Host
+            description: The Revolut Business API hostname for your environment.
+            enum:
+                - b2b.revolut.com
+                - sandbox-b2b.revolut.com
+            doc_section: '#step-1-selecting-your-environment'
+
 ring-central:
     display_name: RingCentral
     categories:
@@ -18969,6 +19826,33 @@ reapit:
             title: ''
             description: ''
             automated: true
+rydership:
+    display_name: RyderShip
+    categories:
+        - e-commerce
+    auth_mode: OAUTH2
+    authorization_url: https://${connectionConfig.environment}/oauth/authorize
+    token_url: https://${connectionConfig.environment}/oauth/token
+    scope_separator: ' '
+    authorization_params:
+        response_type: code
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://${connectionConfig.environment}/api
+    docs: https://nango.dev/docs/api-integrations/rydership
+    setup_guide_url: https://nango.dev/docs/api-integrations/rydership/how-to-register-your-own-rydership-oauth-app
+    connection_config:
+        environment:
+            type: string
+            title: Environment
+            description: The RyderShip environment to connect to.
+            enum:
+                - www.getwhiplash.com
+                - sandbox.whiplash.app
+
 rydoo:
     display_name: Rydoo
     categories:
@@ -19063,6 +19947,74 @@ sage-200:
             description: ''
             automated: true
 
+sage-300-cre:
+    display_name: Sage 300 Construction and Real Estate
+    categories:
+        - accounting
+        - erp
+    auth_mode: TWO_STEP
+    body_format: json
+    token_url: https://${connectionConfig.serverUrl}/api/common/user/authenticate
+    token_params:
+        userid: ${credentials.username}
+        password: ${credentials.password}
+    token_headers:
+        x-dppkey: ${credentials.dppKey}
+    token_response:
+        token: Data
+    proxy:
+        base_url: https://${connectionConfig.serverUrl}
+        headers:
+            x-dppkey: ${credentials.dppKey}
+            x-credentials: ${accessToken}
+            x-databasename: ${connectionConfig.databaseName}
+    docs: https://nango.dev/docs/api-integrations/sage-300-cre
+    docs_connect: https://nango.dev/docs/api-integrations/sage-300-cre/connect
+    connection_config:
+        serverUrl:
+            type: string
+            title: Server Hostname
+            description: Hostname of your Sage 300 CRE Web API server.
+            example: myserver.company.com
+            order: 1
+            prefix: https://
+            doc_section: '#step-1-finding-your-server-hostname-and-company-data-folder'
+        databaseName:
+            type: string
+            title: Company Data Folder Name
+            description: Your Sage 300 CRE company data folder.
+            example: Company1
+            order: 2
+            doc_section: '#step-1-finding-your-server-hostname-and-company-data-folder'
+    integration_config:
+        dppKey:
+            type: string
+            title: DPP License Key
+            description: Sage DPP license key for this integration.
+            secret: true
+            optional: true
+            doc_section: '#step-3-dpp-license-key-only-if-not-already-configured'
+    credentials:
+        dppKey:
+            type: string
+            title: DPP License Key
+            description: Sage DPP license key (XML blob). Usually preconfigured — only fill in if asked to.
+            secret: true
+            optional: true
+            doc_section: '#step-3-dpp-license-key-only-if-not-already-configured'
+        username:
+            type: string
+            title: Username
+            description: Windows username, including the domain.
+            example: CORP\jdoe
+            doc_section: '#step-2-creating-a-dedicated-integration-user'
+        password:
+            type: string
+            title: Password
+            description: Password for the Windows user above.
+            secret: true
+            doc_section: '#step-2-creating-a-dedicated-integration-user'
+
 sage-hr:
     display_name: Sage HR
     categories:
@@ -20056,6 +21008,35 @@ scrapedo:
             pattern: '^[a-zA-Z0-9]+$'
             doc_section: '#step-1-finding-your-api-key'
 
+scrollstash-mcp:
+    display_name: ScrollStash (MCP)
+    categories:
+        - mcp
+    auth_mode: MCP_OAUTH2
+    client_registration: dynamic
+    authorization_url: https://mcp.scrollstash.com/oauth2/authorize
+    token_url: https://mcp.scrollstash.com/oauth2/token
+    registration_url: https://mcp.scrollstash.com/oauth2/register
+    default_scopes:
+        - mcp
+    registration_params:
+        response_types:
+            - code
+        grant_types:
+            - authorization_code
+            - refresh_token
+    authorization_params:
+        response_type: code
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://mcp.scrollstash.com
+        headers:
+            accept: application/json,text/event-stream
+    docs: https://nango.dev/docs/api-integrations/scrollstash-mcp
+
 salesloft:
     display_name: Salesloft
     categories:
@@ -21591,6 +22572,36 @@ splitwise:
         base_url: https://secure.splitwise.com
     docs: https://nango.dev/docs/integrations/all/splitwise
 
+splunk:
+    display_name: Splunk
+    categories:
+        - analytics
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://${connectionConfig.hostname}
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /services/authentication/current-context?output_mode=json
+    docs: https://nango.dev/docs/api-integrations/splunk
+    docs_connect: https://nango.dev/docs/api-integrations/splunk/connect
+    connection_config:
+        hostname:
+            type: string
+            title: Splunk host
+            description: Your Splunk management host and port.
+            example: my-splunk.example.com:8089
+            pattern: '^[a-zA-Z0-9.-]+(:[0-9]+)?$'
+            order: 1
+    credentials:
+        apiKey:
+            type: string
+            title: Authentication Token
+            description: Your Splunk authentication token.
+            doc_section: '#step-1-create-an-authentication-token'
+
 spotify:
     display_name: Spotify (OAuth)
     categories:
@@ -21756,6 +22767,30 @@ statista:
             pattern: '^[a-zA-Z0-9]+$'
             doc_section: '#step-1-finding-your-api-key'
 
+statsig:
+    display_name: Statsig
+    categories:
+        - dev-tools
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://statsigapi.net
+        headers:
+            statsig-api-key: ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /console/v1/users?limit=1&page=1
+    docs: https://nango.dev/docs/api-integrations/statsig
+    docs_connect: https://nango.dev/docs/api-integrations/statsig/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: Your Statsig Console API Key from the Statsig Console.
+            example: console-***************************************amXc
+            pattern: '^console-[A-Za-z0-9]+$'
+            doc_section: '#step-1-get-your-api-key'
+
 stay-ai:
     display_name: Stay AI
     categories:
@@ -21846,6 +22881,31 @@ store-leads:
             pattern: '^[a-zA-Z0-9]{8}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{4}-[a-zA-Z0-9]{8}$'
             example: a174****-****-****-****-****c6ee
 
+stedi:
+    display_name: Stedi (Healthcare)
+    categories:
+        - other
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://healthcare.us.stedi.com
+        headers:
+            authorization: ${apiKey}
+        verification:
+            method: GET
+            headers:
+                content-type: application/json
+            endpoints:
+                - /2024-04-01/payers?pageSize=10
+    docs: https://nango.dev/docs/api-integrations/stedi
+    docs_connect: https://nango.dev/docs/api-integrations/stedi/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: Your Stedi API key.
+            example: test_JX***************48l
+            doc_section: '#step-1-creating-an-api-key'
+
 strava:
     display_name: Strava (Mobile)
     categories:
@@ -21918,6 +22978,61 @@ streak:
             default_value: ''
             hidden: true
 
+streamline-ai:
+    display_name: Streamline AI
+    categories:
+        - legal
+    auth_mode: BASIC
+    proxy:
+        base_url: https://${connectionConfig.customer}.${connectionConfig.domain}/api
+        headers:
+            authorization: 'Signature keyid="${credentials.username}"'
+            content-type: application/json
+            content-digest: 'sha-256=:${sha256Base64(${bodyCanonicalParams})}:'
+            signature-input: 'sig=("@method" "@target-uri" "content-digest" "content-type");alg="ed25519";created=${now:X};expires=${now+1:minutes:X};keyid="${credentials.username}"'
+            signature: "sig=:${ed25519Sign(\"@method\": ${method}\n\"@target-uri\": https://${host}${path}\n\"content-digest\": sha-256=:${sha256Base64(${bodyCanonicalParams})}:\n\"content-type\": application/json\n\"@signature-params\": (\"@method\" \"@target-uri\" \"content-digest\" \"content-type\");alg=\"ed25519\";created=${now:X};expires=${now+1:minutes:X};keyid=\"${credentials.username}\", ${credentials.password})}:"
+        retry:
+            after:
+                - 'retry-after'
+        verification:
+            method: GET
+            endpoints:
+                - /v0/request-forms
+    docs: https://nango.dev/docs/api-integrations/streamline-ai
+    docs_connect: https://nango.dev/docs/api-integrations/streamline-ai/connect
+    connection_config:
+        customer:
+            type: string
+            title: Customer Subdomain
+            description: Your Streamline AI customer subdomain.
+            example: acme
+            pattern: '^[a-z0-9-]+$'
+            order: 1
+            doc_section: '#step-2-find-your-customer-subdomain'
+        domain:
+            type: string
+            title: Environment
+            description: Whether this connection is to your production or demo/sandbox Streamline AI workspace.
+            enum:
+                - streamline.ai
+                - demo.streamline.ai
+            default_value: streamline.ai
+            order: 2
+            doc_section: '#step-2-find-your-customer-subdomain'
+    credentials:
+        username:
+            type: string
+            title: Auth Key ID
+            description: The Auth Key ID shown in Streamline AI after registering your public key.
+            example: slak_ceWnGIU******vfKI-t3ckVCw***************************
+            doc_section: '#step-1-generate-and-register-an-auth-key'
+        password:
+            type: string
+            title: Private Key
+            description: The private key (PEM format) for your Streamline AI Auth Key.
+            secret: true
+            doc_section: '#step-1-generate-and-register-an-auth-key'
+
 stripe:
     display_name: Stripe Connect
     categories:
@@ -23036,6 +24151,93 @@ trafft:
             secret: true
             doc_section: '#step-2-get-your-credentials'
 
+transporeon-carrier-basic:
+    display_name: Transporeon Carrier Interface (Basic Auth)
+    categories:
+        - other
+    auth_mode: BASIC
+    proxy:
+        base_url: https://${connectionConfig.apiHost}/carrier_interface/openapi
+        verification:
+            method: GET
+            endpoints:
+                - /v1/transport
+    docs: https://nango.dev/docs/api-integrations/transporeon-carrier-basic
+    docs_connect: https://nango.dev/docs/api-integrations/transporeon-carrier-basic/connect
+    credentials:
+        username:
+            type: string
+            title: Username
+            description: Your Transporeon username.
+            example: demo@123
+            pattern: '^[^@]+@[^@]+$'
+            doc_section: '#step-1-obtaining-your-credentials'
+        password:
+            type: string
+            title: Password
+            description: Your Transporeon password.
+            secret: true
+            doc_section: '#step-1-obtaining-your-credentials'
+    connection_config:
+        apiHost:
+            type: string
+            title: API Host
+            description: The Transporeon Carrier Interface host to connect to.
+            enum:
+                - xp.transporeon.com
+                - xp.test.transporeon.com
+            doc_section: '#step-2-selecting-your-api-host'
+
+transporeon-carrier-oauth2-cc:
+    display_name: Transporeon Carrier Interface (Client Credentials)
+    categories:
+        - other
+    auth_mode: OAUTH2_CC
+    token_url: https://${connectionConfig.environment}/oauth2/token
+    token_request_auth_method: basic
+    body_format: query
+    token_params:
+        grant_type: client_credentials
+    proxy:
+        base_url: https://${connectionConfig.apiHost}/carrier_interface/openapi
+        verification:
+            method: GET
+            endpoints:
+                - /v1/transport
+    docs: https://nango.dev/docs/api-integrations/transporeon-carrier-oauth2-cc
+    docs_connect: https://nango.dev/docs/api-integrations/transporeon-carrier-oauth2-cc/connect
+    credentials:
+        client_id:
+            type: string
+            title: Client ID
+            description: Your API client ID.
+            example: username@companyId
+            pattern: '^[^@]+@[^@]+$'
+            doc_section: '#step-1-obtaining-your-client-credentials'
+        client_secret:
+            type: string
+            title: Client Secret
+            description: Your API client secret
+            secret: true
+            doc_section: '#step-1-obtaining-your-client-credentials'
+    connection_config:
+        environment:
+            type: string
+            title: Token Host
+            description: The Transporeon OAuth2 token hostname.
+            enum:
+                - api.transporeon.com
+                - api.test.transporeon.com
+            doc_section: '#step-2-selecting-your-token-host-and-api-host'
+        apiHost:
+            type: string
+            title: API Host
+            description: The Transporeon Carrier Interface host to connect to.
+            enum:
+                - xp.transporeon.com
+                - xp.test.transporeon.com
+            doc_section: '#step-2-selecting-your-token-host-and-api-host'
+
 transporeon-oauth2-cc:
     display_name: Transporeon Appointment Scheduling (Client Credentials)
     categories:
@@ -24664,6 +25866,80 @@ videoask:
     docs: https://nango.dev/docs/api-integrations/videoask
     setup_guide_url: https://nango.dev/docs/api-integrations/videoask/how-to-register-your-own-videoask-api-oauth-app
 
+viewpoint-vista:
+    display_name: Viewpoint Vista
+    categories:
+        - erp
+        - accounting
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://api.xchange.trimble.com
+        headers:
+            x-application-key: ${apiKey}
+        connection_config:
+            subscriberCode: ${connectionConfig.subscriberCode}
+    docs: https://nango.dev/docs/api-integrations/viewpoint-vista
+    docs_connect: https://nango.dev/docs/api-integrations/viewpoint-vista/connect
+    credentials:
+        apiKey:
+            type: string
+            title: Application Key
+            description: Your Trimble Xchange Direct API Application Key.
+            format: uuid
+            example: a1b2c3d4-****-****-****-************
+    connection_config:
+        subscriberCode:
+            type: string
+            title: Subscriber Code
+            description: The subscriber code for your Vista account in Trimble Xchange
+            pattern: '^[0-9]+$'
+            example: '34509'
+vincere:
+    display_name: Vincere
+    categories:
+        - hr
+        - ats
+    auth_mode: OAUTH2
+    authorization_url: https://id.vincere.io/oauth2/authorize
+    token_url: https://id.vincere.io/oauth2/token
+    disable_pkce: true
+    authorization_params:
+        response_type: code
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    token_response_metadata:
+        - id_token
+    proxy:
+        base_url: https://${connectionConfig.subdomain}.vincere.io/api
+        headers:
+            id-token: ${credentials.raw.id_token} || ${connectionConfig.id_token}
+            x-api-key: ${connectionConfig.apiKey}
+    docs: https://nango.dev/docs/api-integrations/vincere
+    docs_connect: https://nango.dev/docs/api-integrations/vincere/connect
+    setup_guide_url: https://nango.dev/docs/api-integrations/vincere/how-to-register-your-own-vincere-api-oauth-app
+    connection_config:
+        subdomain:
+            type: string
+            title: Subdomain
+            description: The subdomain of your Vincere tenant.
+            pattern: '^[a-zA-Z0-9-]+$'
+            example: mycompany
+            prefix: https://
+            suffix: .vincere.io
+            doc_section: '#step-1-find-your-vincere-subdomain'
+            order: 1
+        apiKey:
+            type: string
+            title: API Key
+            description: The API key issued by Vincere for your tenant.
+            secret: true
+            format: uuid
+            example: a1b2c3d4-e5f6-47a8-9b0c-d1234567890f
+            doc_section: '#step-2-request-your-api-key'
+            order: 2
+
 wappalyzer:
     display_name: Wappalyzer
     categories:
@@ -25751,6 +27027,54 @@ youtube:
     docs: https://nango.dev/docs/api-integrations/youtube
     setup_guide_url: https://nango.dev/docs/api-integrations/youtube/how-to-register-your-own-youtube-api-oauth-app
 
+yokoy:
+    display_name: Yokoy
+    categories:
+        - accounting
+        - invoicing
+    auth_mode: OAUTH2_CC
+    token_url: https://accounts.${connectionConfig.environment}/oauth2/token
+    token_request_auth_method: basic
+    token_params:
+        grant_type: client_credentials
+    proxy:
+        headers:
+            x-yk-auth-method: yokoy
+        connection_config:
+            organizationId: ${connectionConfig.organizationId}
+        base_url: https://api.${connectionConfig.environment}
+    docs: https://nango.dev/docs/api-integrations/yokoy
+    docs_connect: https://nango.dev/docs/api-integrations/yokoy/connect
+    connection_config:
+        environment:
+            type: string
+            title: Environment
+            description: Your Yokoy environment.
+            enum:
+                - yokoy.ai
+                - test.yokoy.ai
+            doc_section: '#step-3-choose-your-environment'
+            order: 1
+        organizationId:
+            type: string
+            title: Organization ID
+            description: Your Yokoy organization ID.
+            example: 0Ni9IMB000
+            doc_section: '#step-2-find-your-organization-id'
+            order: 2
+    credentials:
+        client_id:
+            type: string
+            title: Client ID
+            description: Your Yokoy client ID.
+            doc_section: '#step-1-generate-your-client-credentials'
+        client_secret:
+            type: string
+            title: Client Secret
+            description: Your Yokoy client secret.
+            doc_section: '#step-1-generate-your-client-credentials'
+            secret: true
+
 zapier:
     display_name: Zapier
     categories: