Skip to main content

HTTP Receiver Connector

HTTP Receiver Connector allows us to send requests to HTTP services in integrations on the MIP platform. With this connector, you can send requests to external HTTP services and perform certain operations based on the responses received. For example, using the HTTP Receiver Connector, a POST request can be sent to an external API to trigger a specific action in integrations. Depending on the answer to this request, various actions can be taken on the MIP platform. For example, you can save information to a specific database if the answer is successful, or handle an error in case of failure. These integrations provide a powerful way to enable cross-system communication and automate workflows.

Required Connector Properties​

  • HTTP Address: The HTTP address includes the basic URL structure of a web service and endpoints representing specific resources or services. This address specifies the functions, resources, and accessible points provided by the service.

  • Method: In HTTP requests, "method" is also referred to as an HTTP method or HTTP verb. The HTTP method specifies the purpose of a request and defines the operation to be performed on a specific resource. HTTP services perform various operations on resources using HTTP methods:

    • GET: Used for reading a resource. It is used to retrieve data from the server without modifying resources.
    • POST: Used to create a new resource. Typically used for resource creation.
    • PUT: Used to update a resource. Often used to update the entire resource.
    • PATCH: Used to update specific fields of a resource. It updates only specific fields, not the entire resource.
    • DELETE: Used to delete a resource.

  • HTTP Timeout: Indicates a time limit applied when an HTTP request does not receive a response within a specified period. The timeout duration is determined by the requesting party and is typically expressed in seconds.

  • Authorization Type: A type of header used to determine whether the requesting user is authorized. This header may include username and password, an API key, or other authentication information to authenticate the identity of the requesting party to the server.

  • Authentication Resource Name: This variable represents pre-recorded username and password information used in services. Each Authentication Resource Name contains authentication information for a user or application.