> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/connectors/areas/business-systems/infor-m3/infor-m3-rest/obtaining-end-point-info-from-infor-ion-api.md).
# Obtaining end-point info from Infor ION API
To establish a connection, you first need to create an **ION API file**. The file is generated under **Authorized Apps** tab inside **Infor ION API** component of **Infor IOS**.
* Click on **+** sign (Add New App) to add a new app to the repository.
Authorized Apps inside Infor ION API
* Provide a **Name** for an authorized application and choose its **Type**. Provide a **Description** and press **Save** to complete the setup.
Creating an authorized app
* The saved application will now have an option to **Download Credentials**. Click on that.
Generating ION API File
* Make sure to set **Create Service Account** and assign an appropriate service user from the list. Click on **Download** to download the ION API file.
Downloading ION API File
* Make sure that the chosen M3 user ID for **Service Account** has proper security roles assigned inside IFS (Infor Federation Services). \
Make sure that either '**GRID-Administrator**' or '**GRID-RunAsM3User**' is ticked. These enable an authenticated user to start jobs on behalf of other users.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.novacuraflow.com/connectors/areas/business-systems/infor-m3/infor-m3-rest/obtaining-end-point-info-from-infor-ion-api.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
