---
schema_version: "1"
id: c7dde1a60a21b8af176e1835f89ef8c1102b66a15e1f75d2569060781d228273
title: Integration Procedure Invocation Using POST (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_integration_procedure_invocation_using_post.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_integration_procedure_invocation_using_post.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c731611312109b2d99447e5f204ba16cfc211891d2f5e2f49e7dbf40a6b552c2
description: For the managed package runtime, to send JSON data to an Integration Procedure, issue a POST call. With a POST call, you can specify inline values in the URL path, append query parameters to the URL, and include a JSON request body.
products:
  - Omnistudio
release: "264"
---
# Integration Procedure Invocation Using POST (Managed Package)

For the managed package runtime, to send JSON data to an Integration Procedure, issue a POST call. With a POST call, you can specify inline values in the URL path, append query parameters to the URL, and include a JSON request body.

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

Use a URL formatted like this:

```
/services/apexrest/{namespace}/v1/integrationprocedure/{Type}_{SubType}/
```

The namespace is `omnistudio`, `vlocity_ins`, `vlocity_cmt`, or `or vlocity_ps`. Specify the Type and SubType of the Integration Procedure.

To pass input data in a POST call, you can specify a JSON request body, pass inline URL path parameters, or append query parameters.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)

Note

When using an Integration Procedure with a REST API, follow these guidelines:

- In JSON notation, curly braces are literal. They delimit JSON objects.
- In REST URL notation, curly braces surround variable values that you must replace. Don't include the braces in an actual request.
- Treat all parts of the REST URL as case-sensitive.

In this example, an Integration Procedure that creates cases requires a Contact name and returns the Id of the newly created case. The Contact name is specified in a JSON request body.

- POST URL:
    
    ```
    /services/apexrest/vlocity_ins/v1/integrationprocedure/Create_Cases/
    ```
- POST JSON data:
    
    ```
    {
      "Contact": "Dennis Reynolds"
    }
    ```
- Result:
    
    ```
    {
      "Case": {
        "Id": "0036100001HDn3QAAT"
      }
    }
    ```

You can pass parameters to as Integration Procedure as part of the URL in two ways:

- Inline values in the URL path
- Appended query parameter=value pairs

For example, the syntax of a URL looks like this:

```
/services/apexrest/{namespace}/v1/integrationprocedure/{Type}_{SubType}/{inlinevalue1}/{inlinevalue2}/?{Param1}={Value1}
```

You can call the URL with these values:

```
/services/apexrest/vlocity_cmt/v1/integrationprocedure/IP_Rest/Apple/Phones/?product=iPhoneX
```

The POST call sends this input to the Integration Procedure. Values passed in the URL path are added under the `options` node of the JSON, with keys named `PathN`.

```
{
  "options": {
    "Path1": "Apple",
    "Path2": "Phones",
    "product": "iPhoneX",
    "isDebug": "true"
  }
}
```

You can also set Integration Procedure options such as `chainable` or `queueableChainable` as query parameters with a REST call:

```
/services/apexrest/vlocity_ins/v1/integrationprocedure/Create_Cases/?queueableChainable=true
```