> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-hermes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm-hermes/integrate/apis/asm-api-quick-reference-guide/creating-new-calls.md). # Creating New Calls ## ASM API Quick Reference Guide #### Start a new Request 1. In Postman, select 'New' in the top left-hand corner. 2. Select HTTP from the dialogue window and give the request the name of **Call Create** ## Creating New Calls 1. **Method**: POST * **URL**: `{{SystemURLTest}}/alemba.api/api/v2/call` * **Full URL**, if desired: `https:////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. Where you have rich text fields (HTML), you always need to provide the **FieldName value** and the **FieldNameHtml value**. 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 : `{` `"CustomString2": "INC5139834",` `"Description": "Description",` `"DescriptionHtml": "

Description

",` `"Ext_BIncExternalSupplierName": "SupplierName",` `"Impact": 10,` `"IpkStatus": 1,` `"IpkStream": 0,` `"Location": 308,` `"Priority":4,` `"Partition": 1,` `"ReceivingGroup":80,` `"Service": 24636,` `"Type": 5,` `"Urgency": 9,` `"User": 38` `}`

A Successful Request

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.alemba.com/asm-hermes/integrate/apis/asm-api-quick-reference-guide/creating-new-calls.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.