@nangohq/providers 0.71.4 → 0.71.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nangohq/providers",
3
- "version": "0.71.4",
3
+ "version": "0.71.5",
4
4
  "description": "Nango's providers.yaml and getters",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
@@ -13,7 +13,7 @@
13
13
  "directory": "packages/providers"
14
14
  },
15
15
  "devDependencies": {
16
- "@nangohq/types": "0.71.4",
16
+ "@nangohq/types": "0.71.5",
17
17
  "vitest": "4.1.9"
18
18
  },
19
19
  "files": [
@@ -22,6 +22,6 @@
22
22
  "providers.scopes.yaml"
23
23
  ],
24
24
  "dependencies": {
25
- "js-yaml": "4.3.0"
25
+ "js-yaml": "4.3.1"
26
26
  }
27
27
  }
@@ -390,6 +390,10 @@ asana:
390
390
  - workspaces:read
391
391
  - workspaces.typeahead:read
392
392
 
393
+ # source: https://docs.intraconnects.com/docs/ehr-basics/athena/Auth/tokenep/ + https://www.stitchflow.com/user-management/athenaone/api + https://mirth.support/blog/athenahealth-integration
394
+ athenahealth:
395
+ - athena/service/Athenanet.MDP.*
396
+
393
397
  # source: https://auth.atlassian.com/.well-known/openid-configuration (scopes_supported) + https://developer.atlassian.com/cloud/jira/platform/scopes-for-connect-and-oauth-2-3LO-apps + https://developer.atlassian.com/cloud/confluence/scopes-for-oauth-2-3LO-and-forge-apps + https://developer.atlassian.com/cloud/jira/service-desk/scopes-for-oauth-2-3LO-and-forge-apps
394
398
  atlassian:
395
399
  - address
@@ -4459,6 +4463,36 @@ helpscout-mailbox: []
4459
4463
  # HeyGen OAuth2 uses Authorization Code Flow with PKCE. No granular scopes documented.
4460
4464
  heygen: []
4461
4465
 
4466
+ # source: HiBob Developer Portal > "Scopes mapping to endpoints" (partner-only page, no public URL)
4467
+ hibob-oauth:
4468
+ - attendance:write
4469
+ - company.metadata:read
4470
+ - company.metadata:write
4471
+ - documents:read
4472
+ - documents:write
4473
+ - employee_data.history:read
4474
+ - employee_data.sensitive.history:read
4475
+ - employee_data.sensitive:read
4476
+ - employee_data.sensitive:write
4477
+ - employee_data:read
4478
+ - employee_data:write
4479
+ - goals:read
4480
+ - goals:write
4481
+ - hiring:write
4482
+ - job_catalog:read
4483
+ - learning.integrations:write
4484
+ - payrollhub.deductions:write
4485
+ - payrollhub.employee_sync:write
4486
+ - payrollhub.payroll:read
4487
+ - projects:write
4488
+ - reports:read
4489
+ - tasks:write
4490
+ - timeoff.sensitive:read
4491
+ - timeoff:read
4492
+ - timeoff:write
4493
+ - workforce_planning:read
4494
+ - workforce_planning:write
4495
+
4462
4496
  # source: https://marketplace.gohighlevel.com/docs/Authorization/Scopes
4463
4497
  highlevel:
4464
4498
  - adPublishing.readOnly
@@ -9877,6 +9911,13 @@ reddit:
9877
9911
  - wikiedit
9878
9912
  - wikiread
9879
9913
 
9914
+ # source: https://developer.revolut.com/docs/business/business-api
9915
+ revolut-business:
9916
+ - READ
9917
+ - WRITE
9918
+ - PAY
9919
+ - READ_SENSITIVE_CARD_DATA
9920
+
9880
9921
  # source: https://platform.ringcentral.com/.well-known/openid-configuration (scopes_supported)
9881
9922
  ring-central:
9882
9923
  - A2PSMS
@@ -9965,6 +10006,11 @@ rippling-shop-app: []
9965
10006
  # source: providers.yaml (no official scopes page or discovery endpoint found)
9966
10007
  roller: []
9967
10008
 
10009
+ # source: https://help.whiplash.com/hc/en-us/articles/360050873291-The-RyderShip-API (scope parameter)
10010
+ rydership:
10011
+ - user_read
10012
+ - user_manage
10013
+
9968
10014
  # source: https://accounts.rydoo.com/.well-known/openid-configuration (scopes_supported)
9969
10015
  rydoo:
9970
10016
  - any_user
package/providers.yaml CHANGED
@@ -814,6 +814,61 @@ affinity-v2:
814
814
  example: 'nrlW2KR5m-qUCA-rTqKb_EUK1swERlenqn70KNMMrTM'
815
815
  doc_section: '#step-1-generating-your-api-key'
816
816
 
817
+ agencyzoom:
818
+ display_name: AgencyZoom
819
+ categories:
820
+ - crm
821
+ auth_mode: TWO_STEP
822
+ body_format: json
823
+ token_url: https://api.agencyzoom.com/v1/api/auth/login
824
+ token_params:
825
+ username: ${credentials.username}
826
+ password: ${credentials.password}
827
+ token_headers:
828
+ content-type: application/json
829
+ accept: application/json
830
+ token_response:
831
+ token: jwt
832
+ proxy:
833
+ base_url: https://api.agencyzoom.com
834
+ docs: https://nango.dev/docs/api-integrations/agencyzoom
835
+ docs_connect: https://nango.dev/docs/api-integrations/agencyzoom/connect
836
+ credentials:
837
+ username:
838
+ type: string
839
+ title: Username
840
+ description: Your AgencyZoom account email address.
841
+ doc_section: '#step-1-obtain-your-credentials'
842
+ password:
843
+ type: string
844
+ title: Password
845
+ description: Your AgencyZoom account password.
846
+ secret: true
847
+ doc_section: '#step-1-obtain-your-credentials'
848
+
849
+ agentline:
850
+ display_name: AgentLine
851
+ categories:
852
+ - communication
853
+ auth_mode: API_KEY
854
+ proxy:
855
+ base_url: https://api.agentline.cloud
856
+ headers:
857
+ authorization: Bearer ${apiKey}
858
+ verification:
859
+ method: GET
860
+ endpoints:
861
+ - /v1/agents
862
+ docs: https://nango.dev/docs/api-integrations/agentline
863
+ docs_connect: https://nango.dev/docs/api-integrations/agentline/connect
864
+ credentials:
865
+ apiKey:
866
+ type: string
867
+ title: API Key
868
+ description: Your AgentLine API key.
869
+ pattern: '^al_live_[a-zA-Z0-9_]+$'
870
+ doc_section: '#step-1-finding-your-api-key'
871
+
817
872
  agiloft:
818
873
  display_name: Agiloft
819
874
  categories:
@@ -1976,6 +2031,53 @@ atlassian:
1976
2031
  base_url: https://api.atlassian.com
1977
2032
  docs: https://nango.dev/docs/integrations/all/atlassian
1978
2033
 
2034
+ athenahealth:
2035
+ display_name: athenahealth
2036
+ categories:
2037
+ - other
2038
+ auth_mode: OAUTH2_CC
2039
+ token_url: https://${connectionConfig.subdomain}.platform.athenahealth.com/oauth2/v1/token
2040
+ token_request_auth_method: basic
2041
+ token_params:
2042
+ grant_type: client_credentials
2043
+ scope_separator: ' '
2044
+ proxy:
2045
+ base_url: https://${connectionConfig.subdomain}.platform.athenahealth.com
2046
+ connection_config:
2047
+ practiceId: ${connectionConfig.practiceId}
2048
+ docs: https://nango.dev/docs/api-integrations/athenahealth
2049
+ docs_connect: https://nango.dev/docs/api-integrations/athenahealth/connect
2050
+ connection_config:
2051
+ subdomain:
2052
+ type: string
2053
+ title: API Environment
2054
+ description: The athenahealth environment to connect to.
2055
+ enum:
2056
+ - api
2057
+ - api.preview
2058
+ doc_section: '#step-2-choose-your-environment'
2059
+ order: 1
2060
+ practiceId:
2061
+ type: string
2062
+ title: Practice ID
2063
+ description: The ID of your athenahealth practice.
2064
+ pattern: '^[0-9]+$'
2065
+ example: '195900'
2066
+ doc_section: '#step-3-find-your-practice-id'
2067
+ order: 2
2068
+ credentials:
2069
+ client_id:
2070
+ type: string
2071
+ title: Client ID
2072
+ description: The client ID for your registered athenahealth app.
2073
+ doc_section: '#step-4-connect-your-athenahealth-account'
2074
+ client_secret:
2075
+ type: string
2076
+ title: Client Secret
2077
+ description: The client secret for your registered athenahealth app.
2078
+ secret: true
2079
+ doc_section: '#step-4-connect-your-athenahealth-account'
2080
+
1979
2081
  atlassian-admin:
1980
2082
  display_name: Atlassian Cloud Admin
1981
2083
  categories:
@@ -2305,13 +2407,10 @@ auvik:
2305
2407
  region:
2306
2408
  type: string
2307
2409
  title: Region
2308
- description: The region of your Auvik account (visible in your browser address bar when logging into the Auvik web UI).
2410
+ 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.
2309
2411
  doc_section: '#step-2-determine-your-region'
2310
- enum:
2311
- - us1
2312
- - us2
2313
- - us6
2314
- - eu1
2412
+ example: us1
2413
+ pattern: '^[a-z0-9-]+$'
2315
2414
  docs: https://nango.dev/docs/integrations/all/auvik
2316
2415
  docs_connect: https://nango.dev/docs/integrations/all/auvik/connect
2317
2416
 
@@ -4321,6 +4420,38 @@ canva-scim:
4321
4420
  description: The API key for your Canva scim account
4322
4421
  doc_section: '#step-1-finding-canva-api-key'
4323
4422
 
4423
+ cdw:
4424
+ display_name: CDW
4425
+ categories:
4426
+ - erp
4427
+ - e-commerce
4428
+ auth_mode: API_KEY
4429
+ proxy:
4430
+ base_url: https://${connectionConfig.baseUrl}
4431
+ headers:
4432
+ subscription-key: ${apiKey}
4433
+ docs: https://nango.dev/docs/api-integrations/cdw
4434
+ docs_connect: https://nango.dev/docs/api-integrations/cdw/connect
4435
+ credentials_verification_script: cdwCredentialsVerification
4436
+ connection_config:
4437
+ baseUrl:
4438
+ type: string
4439
+ title: Environment
4440
+ description: The CDW API gateway you want to connect to.
4441
+ enum:
4442
+ - apiconnect.cdw.com/b2b
4443
+ - apiconnect.preprod.cdw.com/pprd/b2b
4444
+ order: 1
4445
+ doc_section: '#step-3-choosing-your-base-url'
4446
+ credentials:
4447
+ apiKey:
4448
+ type: string
4449
+ title: Subscription Key
4450
+ description: The subscription key from your CDW API Management developer portal account.
4451
+ example: a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4
4452
+ pattern: '^[a-fA-F0-9]{32}$'
4453
+ doc_section: '#step-2-subscribing-to-a-product-and-generating-a-subscription-key'
4454
+
4324
4455
  cerby:
4325
4456
  display_name: Cerby
4326
4457
  categories:
@@ -4444,6 +4575,38 @@ chargebee:
4444
4575
  default_value: ''
4445
4576
  hidden: true
4446
4577
 
4578
+ chartboost:
4579
+ display_name: Chartboost
4580
+ categories:
4581
+ - marketing
4582
+ - gaming
4583
+ auth_mode: OAUTH2_CC
4584
+ body_format: json
4585
+ token_url: https://api.chartboost.com/v5/oauth/token
4586
+ token_params:
4587
+ grant_type: client_credentials
4588
+ audience: https://public.api.gateway.chartboost.com
4589
+ proxy:
4590
+ base_url: https://api.chartboost.com
4591
+ docs: https://nango.dev/docs/api-integrations/chartboost
4592
+ docs_connect: https://nango.dev/docs/api-integrations/chartboost/connect
4593
+ credentials:
4594
+ client_id:
4595
+ type: string
4596
+ title: Client ID
4597
+ description: Your Chartboost API client_id.
4598
+ example: a3f8c1d9b2e47a5c6f0b8d1e3a9c2f
4599
+ pattern: '^[a-f0-9]+$'
4600
+ doc_section: '#step-1-obtain-your-api-credentials'
4601
+ client_secret:
4602
+ type: string
4603
+ title: Client Secret
4604
+ description: Your Chartboost API client_secret.
4605
+ example: a1b2c3d4e5f6********************************************9c8d7e6f
4606
+ pattern: '^[a-f0-9]+$'
4607
+ secret: true
4608
+ doc_section: '#step-1-obtain-your-api-credentials'
4609
+
4447
4610
  chatarmin:
4448
4611
  display_name: Chatarmin
4449
4612
  categories:
@@ -4637,6 +4800,50 @@ checkout-com-sandbox:
4637
4800
  docs: https://nango.dev/docs/integrations/all/checkout-com-sandbox
4638
4801
  docs_connect: https://nango.dev/docs/integrations/all/checkout-com-sandbox/connect
4639
4802
 
4803
+ chili-piper:
4804
+ display_name: Chili Piper
4805
+ categories:
4806
+ - crm
4807
+ auth_mode: API_KEY
4808
+ proxy:
4809
+ base_url: https://fire.chilipiper.com/api/fire-edge
4810
+ headers:
4811
+ authorization: Bearer ${apiKey}
4812
+ verification:
4813
+ method: GET
4814
+ endpoints:
4815
+ - /v1/org/health/ping
4816
+ docs: https://nango.dev/docs/api-integrations/chili-piper
4817
+ docs_connect: https://nango.dev/docs/api-integrations/chili-piper/connect
4818
+ credentials:
4819
+ apiKey:
4820
+ type: string
4821
+ title: API Key
4822
+ description: The API Access Token generated from your Chili Piper account.
4823
+ doc_section: '#step-1-generating-your-api-key'
4824
+
4825
+ chili-piper-mcp:
4826
+ display_name: Chili Piper (MCP)
4827
+ categories:
4828
+ - crm
4829
+ - mcp
4830
+ auth_mode: MCP_OAUTH2
4831
+ client_registration: dynamic
4832
+ authorization_url: https://fire.chilipiper.com/api/fire-edge/v1/oauth/authorize
4833
+ token_url: https://fire.chilipiper.com/api/fire-edge/v1/oauth/token
4834
+ registration_url: https://fire.chilipiper.com/api/fire-edge/v1/oauth/register
4835
+ authorization_params:
4836
+ response_type: code
4837
+ token_params:
4838
+ grant_type: authorization_code
4839
+ refresh_params:
4840
+ grant_type: refresh_token
4841
+ proxy:
4842
+ base_url: https://fire.chilipiper.com/api/fire-edge/v1/org/mcp
4843
+ headers:
4844
+ accept: application/json,text/event-stream
4845
+ docs: https://nango.dev/docs/api-integrations/chili-piper-mcp
4846
+
4640
4847
  chorus:
4641
4848
  display_name: Chorus
4642
4849
  categories:
@@ -7549,6 +7756,26 @@ epic-games:
7549
7756
  base_url: https://api.epicgames.dev
7550
7757
  docs: https://nango.dev/docs/integrations/all/epic-games
7551
7758
 
7759
+ epost-klara:
7760
+ display_name: ePost (KLARA)
7761
+ categories:
7762
+ - other
7763
+ auth_mode: API_KEY
7764
+ proxy:
7765
+ base_url: https://api.klara.ch
7766
+ headers:
7767
+ x-api-key: ${apiKey}
7768
+ docs: https://nango.dev/docs/api-integrations/epost-klara
7769
+ docs_connect: https://nango.dev/docs/api-integrations/epost-klara/connect
7770
+ credentials:
7771
+ apiKey:
7772
+ type: string
7773
+ title: API Key
7774
+ description: Your KLARA API key.
7775
+ format: uuid
7776
+ example: 0b6df221-****-****-****-********e06d
7777
+ doc_section: '#step-1-finding-your-api-key'
7778
+
7552
7779
  ergo:
7553
7780
  display_name: Ergo
7554
7781
  categories:
@@ -7783,7 +8010,7 @@ expensify:
7783
8010
  docs_connect: https://nango.dev/docs/integrations/all/expensify/connect
7784
8011
 
7785
8012
  factorial:
7786
- display_name: Factorial
8013
+ display_name: Factorial (OAuth)
7787
8014
  categories:
7788
8015
  - hr
7789
8016
  auth_mode: OAUTH2
@@ -7794,6 +8021,30 @@ factorial:
7794
8021
  base_url: https://api.factorialhr.com/api
7795
8022
  docs: https://nango.dev/docs/integrations/all/factorial
7796
8023
 
8024
+ factorial-api-key:
8025
+ display_name: Factorial (API Key)
8026
+ categories:
8027
+ - hr
8028
+ auth_mode: API_KEY
8029
+ proxy:
8030
+ base_url: https://api.factorialhr.com/api
8031
+ headers:
8032
+ x-api-key: ${apiKey}
8033
+ verification:
8034
+ method: GET
8035
+ endpoints:
8036
+ - /2026-07-01/resources/api_public/credentials
8037
+ docs: https://nango.dev/docs/api-integrations/factorial-api-key
8038
+ docs_connect: https://nango.dev/docs/api-integrations/factorial-api-key/connect
8039
+ credentials:
8040
+ apiKey:
8041
+ type: string
8042
+ title: API Key
8043
+ description: The API Key generated from your Factorial account
8044
+ example: 'eyJraWQiOiJmYWN.******************************.*****************************'
8045
+ pattern: '^[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+$'
8046
+ doc_section: '#step-1-generating-your-api-key'
8047
+
7797
8048
  fairing:
7798
8049
  display_name: Fairing
7799
8050
  categories:
@@ -8790,6 +9041,24 @@ garmin:
8790
9041
  base_url: https://apis.garmin.com
8791
9042
  docs: https://nango.dev/docs/integrations/all/garmin
8792
9043
 
9044
+ garmin-oauth2:
9045
+ display_name: Garmin (OAuth2)
9046
+ categories:
9047
+ - sports
9048
+ auth_mode: OAUTH2
9049
+ authorization_url: https://connect.garmin.com/oauth2Confirm
9050
+ token_url: https://diauth.garmin.com/di-oauth2-service/oauth/token
9051
+ authorization_params:
9052
+ response_type: code
9053
+ token_params:
9054
+ grant_type: authorization_code
9055
+ refresh_params:
9056
+ grant_type: refresh_token
9057
+ proxy:
9058
+ base_url: https://apis.garmin.com
9059
+ docs: https://nango.dev/docs/api-integrations/garmin-oauth2
9060
+ setup_guide_url: https://nango.dev/docs/api-integrations/garmin-oauth2/how-to-register-your-own-garmin-oauth2-api-oauth-app
9061
+
8793
9062
  gebruder-weiss:
8794
9063
  display_name: Gebrüder Weiss
8795
9064
  categories:
@@ -10454,6 +10723,62 @@ hackerrank-work:
10454
10723
  default_value: ''
10455
10724
  hidden: true
10456
10725
 
10726
+ hail:
10727
+ display_name: Hail
10728
+ categories:
10729
+ - communication
10730
+ - dev-tools
10731
+ - marketing
10732
+ auth_mode: API_KEY
10733
+ proxy:
10734
+ base_url: https://api.hail.so
10735
+ headers:
10736
+ authorization: Bearer ${apiKey}
10737
+ verification:
10738
+ method: GET
10739
+ endpoints:
10740
+ - /calls
10741
+ docs: https://nango.dev/docs/api-integrations/hail
10742
+ docs_connect: https://nango.dev/docs/api-integrations/hail/connect
10743
+ credentials:
10744
+ apiKey:
10745
+ type: string
10746
+ title: API Key
10747
+ description: Your Hail account API key.
10748
+ pattern: '^hl_live_[A-Za-z0-9_-]+$'
10749
+ example: hl_live_************
10750
+ doc_section: '#step-1-getting-your-api-key'
10751
+
10752
+ hail-mcp:
10753
+ display_name: Hail (MCP)
10754
+ categories:
10755
+ - communication
10756
+ - dev-tools
10757
+ - marketing
10758
+ - mcp
10759
+ auth_mode: MCP_OAUTH2
10760
+ client_registration: dynamic
10761
+ authorization_url: https://hail.so/api/auth/oauth2/authorize
10762
+ token_url: https://hail.so/api/auth/oauth2/token
10763
+ registration_url: https://hail.so/api/auth/oauth2/register
10764
+ default_scopes:
10765
+ - offline_access
10766
+ registration_params:
10767
+ grant_types:
10768
+ - authorization_code
10769
+ - refresh_token
10770
+ response_types:
10771
+ - code
10772
+ token_params:
10773
+ grant_type: authorization_code
10774
+ refresh_params:
10775
+ grant_type: refresh_token
10776
+ proxy:
10777
+ base_url: https://mcp.hail.so
10778
+ headers:
10779
+ accept: application/json,text/event-stream
10780
+ docs: https://nango.dev/docs/api-integrations/hail-mcp
10781
+
10457
10782
  haileyhr:
10458
10783
  display_name: Hailey HR
10459
10784
  categories:
@@ -10688,6 +11013,25 @@ hibob-service-user:
10688
11013
  docs: https://nango.dev/docs/integrations/all/hibob-service-user
10689
11014
  docs_connect: https://nango.dev/docs/integrations/all/hibob-service-user/connect
10690
11015
 
11016
+ hibob-oauth:
11017
+ display_name: HiBob (OAuth)
11018
+ categories:
11019
+ - hr
11020
+ auth_mode: OAUTH2
11021
+ authorization_url: https://auth.app.hibob.com/oauth2/v1/apps/authorize
11022
+ token_url: https://auth.app.hibob.com/oauth2/v1/apps/token
11023
+ token_request_auth_method: basic
11024
+ authorization_params:
11025
+ response_type: code
11026
+ token_params:
11027
+ grant_type: authorization_code
11028
+ refresh_params:
11029
+ grant_type: refresh_token
11030
+ scope_separator: ' '
11031
+ proxy:
11032
+ base_url: https://api.hibob.com
11033
+ docs: https://nango.dev/docs/api-integrations/hibob-oauth
11034
+
10691
11035
  heygen:
10692
11036
  display_name: HeyGen
10693
11037
  categories:
@@ -11149,7 +11493,7 @@ instagram:
11149
11493
  - social
11150
11494
  auth_mode: OAUTH2
11151
11495
  scope_separator: ','
11152
- authorization_url: https://api.instagram.com/oauth/authorize
11496
+ authorization_url: https://www.instagram.com/oauth/authorize
11153
11497
  token_url: https://api.instagram.com/oauth/access_token
11154
11498
  refresh_url: https://graph.instagram.com/refresh_access_token
11155
11499
  proxy:
@@ -12758,6 +13102,31 @@ linkhut:
12758
13102
  base_url: https://api.ln.ht
12759
13103
  docs: https://nango.dev/docs/integrations/all/linkhut
12760
13104
 
13105
+ livetennisapi:
13106
+ display_name: Live Tennis API
13107
+ categories:
13108
+ - sports
13109
+ auth_mode: API_KEY
13110
+ proxy:
13111
+ base_url: https://api.livetennisapi.com
13112
+ headers:
13113
+ x-api-key: ${apiKey}
13114
+ accept: application/json
13115
+ verification:
13116
+ method: GET
13117
+ endpoints:
13118
+ - /api/public/v1/matches
13119
+ docs: https://nango.dev/docs/api-integrations/livetennisapi
13120
+ docs_connect: https://nango.dev/docs/api-integrations/livetennisapi/connect
13121
+ credentials:
13122
+ apiKey:
13123
+ type: string
13124
+ title: API Key
13125
+ description: The API key for your Live Tennis API account. It starts with `twjp_`.
13126
+ example: twjp_xxxxxxxxxxxxxxxxxxxx
13127
+ pattern: '^twjp_\S+$'
13128
+ doc_section: '#step-1-generating-your-api-key'
13129
+
12761
13130
  lokalise:
12762
13131
  display_name: Lokalise
12763
13132
  categories:
@@ -13006,8 +13375,37 @@ luma:
13006
13375
  title: API Key
13007
13376
  description: The API key for your Luma account
13008
13377
 
13009
- lumos:
13010
- display_name: Lumos
13378
+ luma-v2:
13379
+ display_name: Luma (v2)
13380
+ categories:
13381
+ - productivity
13382
+ - ticketing
13383
+ auth_mode: API_KEY
13384
+ proxy:
13385
+ headers:
13386
+ x-luma-api-key: ${apiKey}
13387
+ base_url: https://public-api.luma.com
13388
+ retry:
13389
+ after:
13390
+ - 'retry-after'
13391
+ verification:
13392
+ method: GET
13393
+ headers:
13394
+ content-type: application/json
13395
+ endpoints:
13396
+ - /v1/users/get-self
13397
+ docs: https://nango.dev/docs/api-integrations/luma-v2
13398
+ docs_connect: https://nango.dev/docs/api-integrations/luma-v2/connect
13399
+ credentials:
13400
+ apiKey:
13401
+ type: string
13402
+ title: API Key
13403
+ description: The API key for your Luma account
13404
+ pattern: '^secret-[a-zA-Z0-9]+$'
13405
+ example: secret-a1B2c3D4e5F6g7H8i9J0k1L2m
13406
+
13407
+ lumos:
13408
+ display_name: Lumos
13011
13409
  categories:
13012
13410
  - productivity
13013
13411
  auth_mode: API_KEY
@@ -13449,6 +13847,35 @@ medallia:
13449
13847
  default_value: ''
13450
13848
  hidden: true # deprecating this in favor of apiHostUrl
13451
13849
 
13850
+ meilisearch:
13851
+ display_name: Meilisearch
13852
+ categories:
13853
+ - search
13854
+ auth_mode: API_KEY
13855
+ proxy:
13856
+ base_url: ${connectionConfig.instanceUrl}
13857
+ headers:
13858
+ authorization: Bearer ${apiKey}
13859
+ verification:
13860
+ method: GET
13861
+ endpoints:
13862
+ - /version
13863
+ connection_config:
13864
+ instanceUrl:
13865
+ type: string
13866
+ title: Instance URL
13867
+ description: The base URL of your Meilisearch instance.
13868
+ example: https://ms-1a2b3c4d5e6f.meilisearch.io
13869
+ pattern: '^https?://.+[^/]$'
13870
+ order: 1
13871
+ credentials:
13872
+ apiKey:
13873
+ type: string
13874
+ title: API Key
13875
+ description: A Meilisearch API key (not the master key).
13876
+ docs: https://nango.dev/docs/api-integrations/meilisearch
13877
+ docs_connect: https://nango.dev/docs/api-integrations/meilisearch/connect
13878
+
13452
13879
  metabase:
13453
13880
  display_name: Metabase
13454
13881
  categories:
@@ -14750,6 +15177,30 @@ namely-pat:
14750
15177
  description: The Personal Access Token for your Namely account
14751
15178
  doc_section: '#step-2-generating-your-personal-access-token'
14752
15179
 
15180
+ neon:
15181
+ display_name: Neon
15182
+ categories:
15183
+ - dev-tools
15184
+ auth_mode: API_KEY
15185
+ proxy:
15186
+ base_url: https://console.neon.tech/api
15187
+ headers:
15188
+ authorization: Bearer ${apiKey}
15189
+ verification:
15190
+ method: GET
15191
+ endpoints:
15192
+ - /v2/users/me
15193
+ docs: https://nango.dev/docs/api-integrations/neon
15194
+ docs_connect: https://nango.dev/docs/api-integrations/neon/connect
15195
+ credentials:
15196
+ apiKey:
15197
+ type: string
15198
+ title: API Key
15199
+ description: Your Neon API key.
15200
+ pattern: '^(napi_)?[a-z0-9]{64}$'
15201
+ example: napi_1a2b3c4d5e6f****************************************************
15202
+ doc_section: '#step-1-creating-an-api-key'
15203
+
14753
15204
  nerdio:
14754
15205
  display_name: Nerdio
14755
15206
  categories:
@@ -15482,6 +15933,44 @@ okta:
15482
15933
  suffix: .okta.com
15483
15934
  prefix: https://
15484
15935
 
15936
+ okta-api-key:
15937
+ display_name: Okta (API Token)
15938
+ categories:
15939
+ - dev-tools
15940
+ - iam
15941
+ auth_mode: API_KEY
15942
+ proxy:
15943
+ base_url: https://${connectionConfig.hostname}
15944
+ headers:
15945
+ authorization: SSWS ${apiKey}
15946
+ retry:
15947
+ at:
15948
+ - 'x-rate-limit-reset'
15949
+ verification:
15950
+ method: GET
15951
+ endpoints:
15952
+ - /api/v1/users/me
15953
+ docs: https://nango.dev/docs/api-integrations/okta-api-key
15954
+ docs_connect: https://nango.dev/docs/api-integrations/okta-api-key/connect
15955
+ credentials:
15956
+ apiKey:
15957
+ type: string
15958
+ title: API Token
15959
+ description: The API token generated from your Okta org.
15960
+ pattern: '^00[A-Za-z0-9_-]{40}$'
15961
+ example: 00qJ-P************************************
15962
+ doc_section: '#step-1-generating-your-api-token'
15963
+ connection_config:
15964
+ hostname:
15965
+ type: string
15966
+ title: Okta Domain
15967
+ description: The full hostname of your Okta account.
15968
+ format: hostname
15969
+ prefix: https://
15970
+ example: dev-12345678.okta.com
15971
+ order: 1
15972
+ doc_section: '#step-2-finding-your-okta-domain'
15973
+
15485
15974
  okta-cc:
15486
15975
  display_name: Okta (Client Credentials)
15487
15976
  categories:
@@ -15575,6 +16064,41 @@ onlogist:
15575
16064
  description: The API key for your OnLogist account
15576
16065
  doc_section: '#step-1-finding-your-api-key'
15577
16066
 
16067
+ omni:
16068
+ display_name: Omni Analytics
16069
+ categories:
16070
+ - analytics
16071
+ auth_mode: API_KEY
16072
+ proxy:
16073
+ base_url: https://${connectionConfig.subdomain}.omniapp.co/api
16074
+ headers:
16075
+ authorization: Bearer ${apiKey}
16076
+ verification:
16077
+ method: GET
16078
+ headers:
16079
+ content-type: application/json
16080
+ endpoints:
16081
+ - /v1/whoami
16082
+ docs: https://nango.dev/docs/api-integrations/omni
16083
+ docs_connect: https://nango.dev/docs/api-integrations/omni/connect
16084
+ connection_config:
16085
+ subdomain:
16086
+ type: string
16087
+ title: Instance Subdomain
16088
+ description: Your Omni instance subdomain.
16089
+ order: 1
16090
+ pattern: '^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$'
16091
+ example: acme
16092
+ doc_section: '#step-1-finding-your-instance-subdomain'
16093
+ credentials:
16094
+ apiKey:
16095
+ type: string
16096
+ title: API Key
16097
+ description: An Omni Organization API key or Personal Access Token (PAT).
16098
+ pattern: '^omni_[a-z]+_[A-Za-z0-9]+$'
16099
+ example: omni_osk_40S5****************************************Aakd
16100
+ doc_section: '#step-2-creating-an-api-key'
16101
+
15578
16102
  one-drive:
15579
16103
  display_name: OneDrive for Business
15580
16104
  categories:
@@ -17223,6 +17747,42 @@ pushpay-chms-v1:
17223
17747
  secret: true
17224
17748
  doc_section: '#step-2-create-an-api-user'
17225
17749
 
17750
+ pushpay-chms-v2:
17751
+ display_name: Pushpay ChMS (v2)
17752
+ categories:
17753
+ - crm
17754
+ - productivity
17755
+ auth_mode: OAUTH2
17756
+ authorization_url: https://oauth.ccbchurch.com/oauth/authorize
17757
+ token_url: https://api.ccbchurch.com/oauth/token
17758
+ body_format: json
17759
+ disable_pkce: true
17760
+ scope_separator: ' '
17761
+ authorization_params:
17762
+ response_type: code
17763
+ subdomain: ${connectionConfig.subdomain}
17764
+ token_params:
17765
+ grant_type: authorization_code
17766
+ refresh_params:
17767
+ grant_type: refresh_token
17768
+ proxy:
17769
+ base_url: https://api.ccbchurch.com
17770
+ headers:
17771
+ accept: application/vnd.ccbchurch.v2+json
17772
+ docs: https://nango.dev/docs/api-integrations/pushpay-chms-v2
17773
+ docs_connect: https://nango.dev/docs/api-integrations/pushpay-chms-v2/connect
17774
+ setup_guide_url: https://nango.dev/docs/api-integrations/pushpay-chms-v2/how-to-register-your-own-pushpay-chms-v2-oauth-app
17775
+ connection_config:
17776
+ subdomain:
17777
+ type: string
17778
+ title: Church subdomain
17779
+ description: The subdomain for the Pushpay ChMS (Church Community Builder) site to authorize.
17780
+ example: yourchurch
17781
+ pattern: '^[a-zA-Z0-9-]+$'
17782
+ prefix: https://
17783
+ suffix: .ccbchurch.com
17784
+ doc_section: '#step-1-finding-your-church-subdomain'
17785
+
17226
17786
  plain:
17227
17787
  display_name: Plain
17228
17788
  categories:
@@ -18689,6 +19249,41 @@ revivn:
18689
19249
  secret: true
18690
19250
  doc_section: '#step-1-get-your-oauth2-credentials'
18691
19251
 
19252
+ revolut-business:
19253
+ display_name: Revolut Business
19254
+ categories:
19255
+ - banking
19256
+ auth_mode: OAUTH2
19257
+ authorization_url: https://${connectionConfig.authorizeHost}/app-confirm
19258
+ authorization_params:
19259
+ response_type: code
19260
+ disable_pkce: true
19261
+ token_url: https://${connectionConfig.apiHost}/api/1.0/auth/token
19262
+ refresh_url: https://${connectionConfig.apiHost}/api/1.0/auth/token
19263
+ scope_separator: ','
19264
+ proxy:
19265
+ base_url: https://${connectionConfig.apiHost}
19266
+ docs: https://nango.dev/docs/api-integrations/revolut-business
19267
+ docs_connect: https://nango.dev/docs/api-integrations/revolut-business/connect
19268
+ setup_guide_url: https://nango.dev/docs/api-integrations/revolut-business/how-to-register-your-own-revolut-business-api-oauth-app
19269
+ connection_config:
19270
+ authorizeHost:
19271
+ type: string
19272
+ title: Authorization Host
19273
+ description: The Revolut Business authorization hostname for your environment.
19274
+ enum:
19275
+ - business.revolut.com
19276
+ - sandbox-business.revolut.com
19277
+ doc_section: '#step-1-selecting-your-environment'
19278
+ apiHost:
19279
+ type: string
19280
+ title: API Host
19281
+ description: The Revolut Business API hostname for your environment.
19282
+ enum:
19283
+ - b2b.revolut.com
19284
+ - sandbox-b2b.revolut.com
19285
+ doc_section: '#step-1-selecting-your-environment'
19286
+
18692
19287
  ring-central:
18693
19288
  display_name: RingCentral
18694
19289
  categories:
@@ -18969,6 +19564,33 @@ reapit:
18969
19564
  title: ''
18970
19565
  description: ''
18971
19566
  automated: true
19567
+ rydership:
19568
+ display_name: RyderShip
19569
+ categories:
19570
+ - e-commerce
19571
+ auth_mode: OAUTH2
19572
+ authorization_url: https://${connectionConfig.environment}/oauth/authorize
19573
+ token_url: https://${connectionConfig.environment}/oauth/token
19574
+ scope_separator: ' '
19575
+ authorization_params:
19576
+ response_type: code
19577
+ token_params:
19578
+ grant_type: authorization_code
19579
+ refresh_params:
19580
+ grant_type: refresh_token
19581
+ proxy:
19582
+ base_url: https://${connectionConfig.environment}/api
19583
+ docs: https://nango.dev/docs/api-integrations/rydership
19584
+ setup_guide_url: https://nango.dev/docs/api-integrations/rydership/how-to-register-your-own-rydership-oauth-app
19585
+ connection_config:
19586
+ environment:
19587
+ type: string
19588
+ title: Environment
19589
+ description: The RyderShip environment to connect to.
19590
+ enum:
19591
+ - www.getwhiplash.com
19592
+ - sandbox.whiplash.app
19593
+
18972
19594
  rydoo:
18973
19595
  display_name: Rydoo
18974
19596
  categories:
@@ -19063,6 +19685,74 @@ sage-200:
19063
19685
  description: ''
19064
19686
  automated: true
19065
19687
 
19688
+ sage-300-cre:
19689
+ display_name: Sage 300 Construction and Real Estate
19690
+ categories:
19691
+ - accounting
19692
+ - erp
19693
+ auth_mode: TWO_STEP
19694
+ body_format: json
19695
+ token_url: https://${connectionConfig.serverUrl}/api/common/user/authenticate
19696
+ token_params:
19697
+ userid: ${credentials.username}
19698
+ password: ${credentials.password}
19699
+ token_headers:
19700
+ x-dppkey: ${credentials.dppKey}
19701
+ token_response:
19702
+ token: Data
19703
+ proxy:
19704
+ base_url: https://${connectionConfig.serverUrl}
19705
+ headers:
19706
+ x-dppkey: ${credentials.dppKey}
19707
+ x-credentials: ${accessToken}
19708
+ x-databasename: ${connectionConfig.databaseName}
19709
+ docs: https://nango.dev/docs/api-integrations/sage-300-cre
19710
+ docs_connect: https://nango.dev/docs/api-integrations/sage-300-cre/connect
19711
+ connection_config:
19712
+ serverUrl:
19713
+ type: string
19714
+ title: Server Hostname
19715
+ description: Hostname of your Sage 300 CRE Web API server.
19716
+ example: myserver.company.com
19717
+ order: 1
19718
+ prefix: https://
19719
+ doc_section: '#step-1-finding-your-server-hostname-and-company-data-folder'
19720
+ databaseName:
19721
+ type: string
19722
+ title: Company Data Folder Name
19723
+ description: Your Sage 300 CRE company data folder.
19724
+ example: Company1
19725
+ order: 2
19726
+ doc_section: '#step-1-finding-your-server-hostname-and-company-data-folder'
19727
+ integration_config:
19728
+ dppKey:
19729
+ type: string
19730
+ title: DPP License Key
19731
+ description: Sage DPP license key for this integration.
19732
+ secret: true
19733
+ optional: true
19734
+ doc_section: '#step-3-dpp-license-key-only-if-not-already-configured'
19735
+ credentials:
19736
+ dppKey:
19737
+ type: string
19738
+ title: DPP License Key
19739
+ description: Sage DPP license key (XML blob). Usually preconfigured — only fill in if asked to.
19740
+ secret: true
19741
+ optional: true
19742
+ doc_section: '#step-3-dpp-license-key-only-if-not-already-configured'
19743
+ username:
19744
+ type: string
19745
+ title: Username
19746
+ description: Windows username, including the domain.
19747
+ example: CORP\jdoe
19748
+ doc_section: '#step-2-creating-a-dedicated-integration-user'
19749
+ password:
19750
+ type: string
19751
+ title: Password
19752
+ description: Password for the Windows user above.
19753
+ secret: true
19754
+ doc_section: '#step-2-creating-a-dedicated-integration-user'
19755
+
19066
19756
  sage-hr:
19067
19757
  display_name: Sage HR
19068
19758
  categories:
@@ -21591,6 +22281,36 @@ splitwise:
21591
22281
  base_url: https://secure.splitwise.com
21592
22282
  docs: https://nango.dev/docs/integrations/all/splitwise
21593
22283
 
22284
+ splunk:
22285
+ display_name: Splunk
22286
+ categories:
22287
+ - analytics
22288
+ auth_mode: API_KEY
22289
+ proxy:
22290
+ base_url: https://${connectionConfig.hostname}
22291
+ headers:
22292
+ authorization: Bearer ${apiKey}
22293
+ verification:
22294
+ method: GET
22295
+ endpoints:
22296
+ - /services/authentication/current-context?output_mode=json
22297
+ docs: https://nango.dev/docs/api-integrations/splunk
22298
+ docs_connect: https://nango.dev/docs/api-integrations/splunk/connect
22299
+ connection_config:
22300
+ hostname:
22301
+ type: string
22302
+ title: Splunk host
22303
+ description: Your Splunk management host and port.
22304
+ example: my-splunk.example.com:8089
22305
+ pattern: '^[a-zA-Z0-9.-]+(:[0-9]+)?$'
22306
+ order: 1
22307
+ credentials:
22308
+ apiKey:
22309
+ type: string
22310
+ title: Authentication Token
22311
+ description: Your Splunk authentication token.
22312
+ doc_section: '#step-1-create-an-authentication-token'
22313
+
21594
22314
  spotify:
21595
22315
  display_name: Spotify (OAuth)
21596
22316
  categories:
@@ -21756,6 +22476,30 @@ statista:
21756
22476
  pattern: '^[a-zA-Z0-9]+$'
21757
22477
  doc_section: '#step-1-finding-your-api-key'
21758
22478
 
22479
+ statsig:
22480
+ display_name: Statsig
22481
+ categories:
22482
+ - dev-tools
22483
+ auth_mode: API_KEY
22484
+ proxy:
22485
+ base_url: https://statsigapi.net
22486
+ headers:
22487
+ statsig-api-key: ${apiKey}
22488
+ verification:
22489
+ method: GET
22490
+ endpoints:
22491
+ - /console/v1/users?limit=1&page=1
22492
+ docs: https://nango.dev/docs/api-integrations/statsig
22493
+ docs_connect: https://nango.dev/docs/api-integrations/statsig/connect
22494
+ credentials:
22495
+ apiKey:
22496
+ type: string
22497
+ title: API Key
22498
+ description: Your Statsig Console API Key from the Statsig Console.
22499
+ example: console-***************************************amXc
22500
+ pattern: '^console-[A-Za-z0-9]+$'
22501
+ doc_section: '#step-1-get-your-api-key'
22502
+
21759
22503
  stay-ai:
21760
22504
  display_name: Stay AI
21761
22505
  categories:
@@ -21846,6 +22590,31 @@ store-leads:
21846
22590
  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}$'
21847
22591
  example: a174****-****-****-****-****c6ee
21848
22592
 
22593
+ stedi:
22594
+ display_name: Stedi (Healthcare)
22595
+ categories:
22596
+ - other
22597
+ auth_mode: API_KEY
22598
+ proxy:
22599
+ base_url: https://healthcare.us.stedi.com
22600
+ headers:
22601
+ authorization: ${apiKey}
22602
+ verification:
22603
+ method: GET
22604
+ headers:
22605
+ content-type: application/json
22606
+ endpoints:
22607
+ - /2024-04-01/payers?pageSize=10
22608
+ docs: https://nango.dev/docs/api-integrations/stedi
22609
+ docs_connect: https://nango.dev/docs/api-integrations/stedi/connect
22610
+ credentials:
22611
+ apiKey:
22612
+ type: string
22613
+ title: API Key
22614
+ description: Your Stedi API key.
22615
+ example: test_JX***************48l
22616
+ doc_section: '#step-1-creating-an-api-key'
22617
+
21849
22618
  strava:
21850
22619
  display_name: Strava (Mobile)
21851
22620
  categories:
@@ -21918,6 +22687,61 @@ streak:
21918
22687
  default_value: ''
21919
22688
  hidden: true
21920
22689
 
22690
+ streamline-ai:
22691
+ display_name: Streamline AI
22692
+ categories:
22693
+ - legal
22694
+ auth_mode: BASIC
22695
+ proxy:
22696
+ base_url: https://${connectionConfig.customer}.${connectionConfig.domain}/api
22697
+ headers:
22698
+ authorization: 'Signature keyid="${credentials.username}"'
22699
+ content-type: application/json
22700
+ content-digest: 'sha-256=:${sha256Base64(${bodyCanonicalParams})}:'
22701
+ signature-input: 'sig=("@method" "@target-uri" "content-digest" "content-type");alg="ed25519";created=${now:X};expires=${now+1:minutes:X};keyid="${credentials.username}"'
22702
+ 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})}:"
22703
+ retry:
22704
+ after:
22705
+ - 'retry-after'
22706
+ verification:
22707
+ method: GET
22708
+ endpoints:
22709
+ - /v0/request-forms
22710
+ docs: https://nango.dev/docs/api-integrations/streamline-ai
22711
+ docs_connect: https://nango.dev/docs/api-integrations/streamline-ai/connect
22712
+ connection_config:
22713
+ customer:
22714
+ type: string
22715
+ title: Customer Subdomain
22716
+ description: Your Streamline AI customer subdomain.
22717
+ example: acme
22718
+ pattern: '^[a-z0-9-]+$'
22719
+ order: 1
22720
+ doc_section: '#step-2-find-your-customer-subdomain'
22721
+ domain:
22722
+ type: string
22723
+ title: Environment
22724
+ description: Whether this connection is to your production or demo/sandbox Streamline AI workspace.
22725
+ enum:
22726
+ - streamline.ai
22727
+ - demo.streamline.ai
22728
+ default_value: streamline.ai
22729
+ order: 2
22730
+ doc_section: '#step-2-find-your-customer-subdomain'
22731
+ credentials:
22732
+ username:
22733
+ type: string
22734
+ title: Auth Key ID
22735
+ description: The Auth Key ID shown in Streamline AI after registering your public key.
22736
+ example: slak_ceWnGIU******vfKI-t3ckVCw***************************
22737
+ doc_section: '#step-1-generate-and-register-an-auth-key'
22738
+ password:
22739
+ type: string
22740
+ title: Private Key
22741
+ description: The private key (PEM format) for your Streamline AI Auth Key.
22742
+ secret: true
22743
+ doc_section: '#step-1-generate-and-register-an-auth-key'
22744
+
21921
22745
  stripe:
21922
22746
  display_name: Stripe Connect
21923
22747
  categories:
@@ -23036,6 +23860,93 @@ trafft:
23036
23860
  secret: true
23037
23861
  doc_section: '#step-2-get-your-credentials'
23038
23862
 
23863
+ transporeon-carrier-basic:
23864
+ display_name: Transporeon Carrier Interface (Basic Auth)
23865
+ categories:
23866
+ - other
23867
+ auth_mode: BASIC
23868
+ proxy:
23869
+ base_url: https://${connectionConfig.apiHost}/carrier_interface/openapi
23870
+ verification:
23871
+ method: GET
23872
+ endpoints:
23873
+ - /v1/transport
23874
+ docs: https://nango.dev/docs/api-integrations/transporeon-carrier-basic
23875
+ docs_connect: https://nango.dev/docs/api-integrations/transporeon-carrier-basic/connect
23876
+ credentials:
23877
+ username:
23878
+ type: string
23879
+ title: Username
23880
+ description: Your Transporeon username.
23881
+ example: demo@123
23882
+ pattern: '^[^@]+@[^@]+$'
23883
+ doc_section: '#step-1-obtaining-your-credentials'
23884
+ password:
23885
+ type: string
23886
+ title: Password
23887
+ description: Your Transporeon password.
23888
+ secret: true
23889
+ doc_section: '#step-1-obtaining-your-credentials'
23890
+ connection_config:
23891
+ apiHost:
23892
+ type: string
23893
+ title: API Host
23894
+ description: The Transporeon Carrier Interface host to connect to.
23895
+ enum:
23896
+ - xp.transporeon.com
23897
+ - xp.test.transporeon.com
23898
+ doc_section: '#step-2-selecting-your-api-host'
23899
+
23900
+ transporeon-carrier-oauth2-cc:
23901
+ display_name: Transporeon Carrier Interface (Client Credentials)
23902
+ categories:
23903
+ - other
23904
+ auth_mode: OAUTH2_CC
23905
+ token_url: https://${connectionConfig.environment}/oauth2/token
23906
+ token_request_auth_method: basic
23907
+ body_format: query
23908
+ token_params:
23909
+ grant_type: client_credentials
23910
+ proxy:
23911
+ base_url: https://${connectionConfig.apiHost}/carrier_interface/openapi
23912
+ verification:
23913
+ method: GET
23914
+ endpoints:
23915
+ - /v1/transport
23916
+ docs: https://nango.dev/docs/api-integrations/transporeon-carrier-oauth2-cc
23917
+ docs_connect: https://nango.dev/docs/api-integrations/transporeon-carrier-oauth2-cc/connect
23918
+ credentials:
23919
+ client_id:
23920
+ type: string
23921
+ title: Client ID
23922
+ description: Your API client ID.
23923
+ example: username@companyId
23924
+ pattern: '^[^@]+@[^@]+$'
23925
+ doc_section: '#step-1-obtaining-your-client-credentials'
23926
+ client_secret:
23927
+ type: string
23928
+ title: Client Secret
23929
+ description: Your API client secret
23930
+ secret: true
23931
+ doc_section: '#step-1-obtaining-your-client-credentials'
23932
+ connection_config:
23933
+ environment:
23934
+ type: string
23935
+ title: Token Host
23936
+ description: The Transporeon OAuth2 token hostname.
23937
+ enum:
23938
+ - api.transporeon.com
23939
+ - api.test.transporeon.com
23940
+ doc_section: '#step-2-selecting-your-token-host-and-api-host'
23941
+ apiHost:
23942
+ type: string
23943
+ title: API Host
23944
+ description: The Transporeon Carrier Interface host to connect to.
23945
+ enum:
23946
+ - xp.transporeon.com
23947
+ - xp.test.transporeon.com
23948
+ doc_section: '#step-2-selecting-your-token-host-and-api-host'
23949
+
23039
23950
  transporeon-oauth2-cc:
23040
23951
  display_name: Transporeon Appointment Scheduling (Client Credentials)
23041
23952
  categories:
@@ -24664,6 +25575,80 @@ videoask:
24664
25575
  docs: https://nango.dev/docs/api-integrations/videoask
24665
25576
  setup_guide_url: https://nango.dev/docs/api-integrations/videoask/how-to-register-your-own-videoask-api-oauth-app
24666
25577
 
25578
+ viewpoint-vista:
25579
+ display_name: Viewpoint Vista
25580
+ categories:
25581
+ - erp
25582
+ - accounting
25583
+ auth_mode: API_KEY
25584
+ proxy:
25585
+ base_url: https://api.xchange.trimble.com
25586
+ headers:
25587
+ x-application-key: ${apiKey}
25588
+ connection_config:
25589
+ subscriberCode: ${connectionConfig.subscriberCode}
25590
+ docs: https://nango.dev/docs/api-integrations/viewpoint-vista
25591
+ docs_connect: https://nango.dev/docs/api-integrations/viewpoint-vista/connect
25592
+ credentials:
25593
+ apiKey:
25594
+ type: string
25595
+ title: Application Key
25596
+ description: Your Trimble Xchange Direct API Application Key.
25597
+ format: uuid
25598
+ example: a1b2c3d4-****-****-****-************
25599
+ connection_config:
25600
+ subscriberCode:
25601
+ type: string
25602
+ title: Subscriber Code
25603
+ description: The subscriber code for your Vista account in Trimble Xchange
25604
+ pattern: '^[0-9]+$'
25605
+ example: '34509'
25606
+ vincere:
25607
+ display_name: Vincere
25608
+ categories:
25609
+ - hr
25610
+ - ats
25611
+ auth_mode: OAUTH2
25612
+ authorization_url: https://id.vincere.io/oauth2/authorize
25613
+ token_url: https://id.vincere.io/oauth2/token
25614
+ disable_pkce: true
25615
+ authorization_params:
25616
+ response_type: code
25617
+ token_params:
25618
+ grant_type: authorization_code
25619
+ refresh_params:
25620
+ grant_type: refresh_token
25621
+ token_response_metadata:
25622
+ - id_token
25623
+ proxy:
25624
+ base_url: https://${connectionConfig.subdomain}.vincere.io/api
25625
+ headers:
25626
+ id-token: ${credentials.raw.id_token} || ${connectionConfig.id_token}
25627
+ x-api-key: ${connectionConfig.apiKey}
25628
+ docs: https://nango.dev/docs/api-integrations/vincere
25629
+ docs_connect: https://nango.dev/docs/api-integrations/vincere/connect
25630
+ setup_guide_url: https://nango.dev/docs/api-integrations/vincere/how-to-register-your-own-vincere-api-oauth-app
25631
+ connection_config:
25632
+ subdomain:
25633
+ type: string
25634
+ title: Subdomain
25635
+ description: The subdomain of your Vincere tenant.
25636
+ pattern: '^[a-zA-Z0-9-]+$'
25637
+ example: mycompany
25638
+ prefix: https://
25639
+ suffix: .vincere.io
25640
+ doc_section: '#step-1-find-your-vincere-subdomain'
25641
+ order: 1
25642
+ apiKey:
25643
+ type: string
25644
+ title: API Key
25645
+ description: The API key issued by Vincere for your tenant.
25646
+ secret: true
25647
+ format: uuid
25648
+ example: a1b2c3d4-e5f6-47a8-9b0c-d1234567890f
25649
+ doc_section: '#step-2-request-your-api-key'
25650
+ order: 2
25651
+
24667
25652
  wappalyzer:
24668
25653
  display_name: Wappalyzer
24669
25654
  categories:
@@ -25751,6 +26736,54 @@ youtube:
25751
26736
  docs: https://nango.dev/docs/api-integrations/youtube
25752
26737
  setup_guide_url: https://nango.dev/docs/api-integrations/youtube/how-to-register-your-own-youtube-api-oauth-app
25753
26738
 
26739
+ yokoy:
26740
+ display_name: Yokoy
26741
+ categories:
26742
+ - accounting
26743
+ - invoicing
26744
+ auth_mode: OAUTH2_CC
26745
+ token_url: https://accounts.${connectionConfig.environment}/oauth2/token
26746
+ token_request_auth_method: basic
26747
+ token_params:
26748
+ grant_type: client_credentials
26749
+ proxy:
26750
+ headers:
26751
+ x-yk-auth-method: yokoy
26752
+ connection_config:
26753
+ organizationId: ${connectionConfig.organizationId}
26754
+ base_url: https://api.${connectionConfig.environment}
26755
+ docs: https://nango.dev/docs/api-integrations/yokoy
26756
+ docs_connect: https://nango.dev/docs/api-integrations/yokoy/connect
26757
+ connection_config:
26758
+ environment:
26759
+ type: string
26760
+ title: Environment
26761
+ description: Your Yokoy environment.
26762
+ enum:
26763
+ - yokoy.ai
26764
+ - test.yokoy.ai
26765
+ doc_section: '#step-3-choose-your-environment'
26766
+ order: 1
26767
+ organizationId:
26768
+ type: string
26769
+ title: Organization ID
26770
+ description: Your Yokoy organization ID.
26771
+ example: 0Ni9IMB000
26772
+ doc_section: '#step-2-find-your-organization-id'
26773
+ order: 2
26774
+ credentials:
26775
+ client_id:
26776
+ type: string
26777
+ title: Client ID
26778
+ description: Your Yokoy client ID.
26779
+ doc_section: '#step-1-generate-your-client-credentials'
26780
+ client_secret:
26781
+ type: string
26782
+ title: Client Secret
26783
+ description: Your Yokoy client secret.
26784
+ doc_section: '#step-1-generate-your-client-credentials'
26785
+ secret: true
26786
+
25754
26787
  zapier:
25755
26788
  display_name: Zapier
25756
26789
  categories: