Integration profile
Discovery provider · Generic REST API
Discover CIs from a governed REST API with explicit authentication, paging, and mapping.
Demo baseline · November 13, 2026Prerequisites
- API documentation and stable resource endpoint
- Read-only API identity
- Sample response for mapping and pagination tests
Configuration steps
- Configure URL and authentication
- Define resource path, paging, and rate limit
- Map response properties to CMDB fields
- Test a preview before scheduling
Provider fields
| Field | Type | Requirement and options |
|---|---|---|
Base URLbaseUrl | url | Required |
Authentication schemeauthScheme | select | Requiredoauth2_client_credentials, bearer_token, api_key, basic, mtls, none |
OAuth token URLtokenUrl | url | Optional |
OAuth client IDclientId | text | Optional |
Credential secret aliascredentialSecretAlias | text | Optional |
Resource pathresourcePath | text | Required |
Pagination strategypagination | select | Requirednone, page_number, offset_limit, cursor, link_header |
Header secret aliasrequestHeadersSecretAlias | text | Optional |
Request templaterequestTemplate | textarea | Optional |
Response-to-CMDB mappingresponseMapping | textarea | Required |
Rate limit / minuterateLimitPerMinute | number | Optional |
Collector / MID servercollector | text | Optional |
Verify and troubleshoot
Test with the narrowest supported non-production scope. Confirm that the connection test reaches the expected provider and that the preview or receipt matches the intended scope. Check identity, credential references, network access and provider permissions before retrying. Record the failure stage and redact sensitive payloads when escalating.