> For the complete documentation index, see [llms.txt](https://docs.fieldmotion.com/fieldmotion-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fieldmotion.com/fieldmotion-api-docs/job/_getstock.md).

# \_getStock

Return information about stock assigned to the Job.

### Parameters

#### id

The ID of the Job to check.

### Example

```
FM_api('Job_getStock', ['id' => '780']);
```

### Result

#### On Success

```
{'general':[
  {'id':'4',
   'amt':'2',
   'containers':
     {'1_32':2}
  }
 ],
 'fieldspecific':[
   {'id':7,
    'amt':3,
    'source':'user'},
   {'id':7,
    'amt':1,
    'source':'user'}
 ]}
```

Note that the returned object has two fields. The "general" array is an array of stock items that are assigned to the job itself. The "fieldspecific" array is items that were assigned within a table in the form itself.

#### On Failure

If no ID is supplied:

```
{'error':'no ID supplied'}
```

If the specified Job does not exist:

```
{'error':'Requested job does not exist'}
```


---

# 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.fieldmotion.com/fieldmotion-api-docs/job/_getstock.md?ask=<question>&goal=<endgoal>
```

`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.