# Creating New Calls

## ASM API Quick Reference Guide <a href="#asmapiquickreferenceguide" id="asmapiquickreferenceguide"></a>

#### Start a new Request  <a href="#lockingandupdatingcalls" id="lockingandupdatingcalls"></a>

1. In Postman, select 'New' in the top left-hand corner.&#x20;
2. Select HTTP from the dialogue window and give the request the name of **Call Create**

## Creating New Calls <a href="#creatingnewcalls" id="creatingnewcalls"></a>

1. **Method**: POST

   * **URL**: `{{SystemURLTest}}/alemba.api/api/v2/call`
     * **Full URL**, if desired: `https://<yourservername>/<yourASMsystemname>/alemba.api/api/v2/call`
   * **Headers**: `Content-Type: application/json`
   * **Authorization:** `Bearer {{Login_Token}}`
   * **Body**: `Raw`
   * **Body:** JSON data with required fields such as `IpkStatus`, `IpkStream`, `Partition`, `Type`, `Urgency`, `Priority`, `Impact`, `Description`, `Service`, `User`, and `ReceivingGroup`.

   The Body of the HTTP request is where you enter the data/changes that you want to enact on the call. The Body is written in JSON. See[ Jargon Buster](/asm-hermes/integrate/apis/asm-api-quick-reference-guide.md#jargonbuster) to read more about JSON.

{% hint style="warning" %}
There are a number of parameters that MUST be provided when creating a new call such as:

* IpkStatus
* IpkStream
* Partition
* Type
* Urgency
* Priority
* Impact
* Description
* DescriptionHtml
* Service
* User
* ReceivingGroup

**Please note:**

1. &#x20;Where you have rich text fields (HTML), you always need to provide the **FieldName value** and the **FieldNameHtml value**.&#x20;
2. Custom fields will always have a **Ext\_** in front of their normal name value
3. Names with spaces will have spaces removed e.g. B Inc External Supplier Name becomes **Ext\_BIncExternalSupplierName**
   {% endhint %}

The JSON body may look like this :

`{`

&#x20;       `"CustomString2": "INC5139834",`

&#x20;       `"Description": "Description",`

&#x20;       `"DescriptionHtml": "<p>Description</p>",`

&#x20;       `"Ext_BIncExternalSupplierName": "SupplierName",`

&#x20;       `"Impact": 10,`

&#x20;       `"IpkStatus": 1,`

&#x20;       `"IpkStream": 0,`

&#x20;       `"Location": 308,`

&#x20;       `"Priority":4,`

&#x20;       `"Partition": 1,`

&#x20;       `"ReceivingGroup":80,`

&#x20;       `"Service": 24636,`

&#x20;       `"Type": 5,`

&#x20;       `"Urgency": 9,`

&#x20;       `"User": 38`

&#x20;`}`

<figure><img src="/files/XwkvxSpsK9XkQoGn0ivu" alt=""><figcaption><p>A Successful Request</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.alemba.com/asm-hermes/integrate/apis/asm-api-quick-reference-guide/creating-new-calls.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.