Endpoint details
In this document, you will find detailed info about the 4me Endpoint Type. This Endpoint Type is a Self-Service type, so users can add them without a need to reach out to ONEiO Support.
| General | |
|---|---|
| Status | Sets the status of the endpoint. Active / Suspended |
| 4me root URL | The base address of your 4me. You can test the HTTP connection by clicking the Test Connection button. Note that this function does not test the authentication, only if ONEiO can reach the endpoint. |
| Name | Name of the endpoint. It is recommended to use short names since this name is used in displays throughout ONEiO. |
| Timezone | The timezone used in the 4me instance. |
| Datetime pattern | Date time pattern ONEiO uses to read DateTime fields and how ONEiO sends out DateTime fields. Shown only for reference. |
| [Your4me] -> ONEiO | |
|---|---|
| Receiver address | The address to insert to 4me's Webhook. The targets are different when operating in QA or Production.
Note that credentials need to be added directly to the URL
|
| Username | Username (and password) to be used in 4me's HTTP target Url. You can reset/retrieve a password in edit mode. |
| ONEiO -> [Your4me] | |
|---|---|
| 4me username | The user that is used in all calls to 4me's API. These include updates and lookups. |
| Password | The password of the 4me user |
| Unrecoverable HTTP error codes | List of numeric HTTP response codes that are to be handled as non-recoverable when sending messages to 4me's API. If ONEiO receives an error code that is not on the list, it will retry the message automatically. If ONEiO receives an error code that IS on this list, the message will result in an error. |
Entity types
To integrate with 4me, you can use only fixed Entity types. This is due to the fact that the entities available are dependent on available APIs in 4me. Currently supported entity types:
- Request
Comments
Please sign in to leave a comment.