Documentation Index

Fetch the complete documentation index at: https://help.idibilling.com/llms.txt

Use this file to discover all available pages before exploring further.

IDI version 26.8 is now available.  Click here for details: IDI Updates.

Provisioning – Standard Provider

Prev Next

Summary

The article will review the specifications and actions supported under the Standard provider. The Standard provider is used to collect generic actions that can call multiple endpoints.

“Standard” is the Provider name used on the Provider Settings page. When selecting the Provider on the Profile screen, the name of the Provider may vary based on the action.

Available Actions

Provider

Action

Available

HTTP Provider

Make HTTP Request

21.2

Action Detail

The section below reviews the available parameters for the supported action.

Make HTTP Request

The Make HTTP Request action will perform an HTTP request from the Provisioning system to a specified address. It allows you to specify the method, the body of the request, as well as any desired HTTP headers.

Using the Make HTTP Request action, you can:

  • Easily integrate with CostGuard APIs

  • Integrate with arbitrary third-party APIs

  • Achieve greater flexibility than the existing Web API action

Name

Type

Required*

Notes

Address

String

Yes

The address to which the HTTP request should be made

Method

List

Yes

The HTTP method to use when making the request. Supported methods are: GET, DELETE, PATCH, POST, PUT.

Headers

 

 

 

Include IDI Security Token

Boolean

No

If set to “Yes”, the request send will include an Authorization header that specifies a token that will allow integration with other CostGuard APIs. Note that this will take precedence over the Authorization parameter, as well as any “Authorization” headers specified in Additional Headers.

Authorization

String

No

The value specified here will be sent as the value of the Authorization header in the request. Note that this will take precedence over any “Authorization” headers specified in Additional Headers.

Content-Type

String

No

The value specified here will be sent as the value of the Content-Type header in the request.

Additional Headers

String

No

A JSON object that represents any additional headers to be sent in the request. (The keys of the object should be the name of the HTTP header; the values should be the value of the header.)

Body

String

No

The body of the request.