Sign Out from the Service

Each time your application finishes working with the MYOB Acumatica contract-based REST service, you have to sign out from MYOB Acumatica. To sign out from MYOB Acumatica, you access the needed URL address with the POST HTTP method. See the following sections for details on the request and the response.

HTTP Method and URL

When you need to sign out from MYOB Acumatica, you use the POST HTTP method and the following URL.

POST http://<MYOB Acumatica instance URL>/entity/auth/logout

You replace <MYOB Acumatica instance URL> with the URL of your MYOB Acumatica instance.

For example, suppose that you want to sign out from a local MYOB Acumatica instance with the name AcumaticaDB. You should use the following HTTP method and URL.

POST http://localhost/AcumaticaDB/entity/auth/logout

Parameters

You use no parameters when you sign out from MYOB Acumatica.

Request Headers

You do not specify any header in the request.

Response Status Codes

The following table lists the HTTP status codes that the system returns for a sign-out request.


Code	Description
204	The request has been completed successfully.
400	The data specified in the request is invalid.
429	The number of requests has exceeded the limit imposed by the license (see License Restrictions for API Users).
500	An internal server error has occurred.

Example

The following request shows an example of a sign out from MYOB Acumatica through the REST API.

Tip:

In the request example below, <MYOB Acumatica instance URL> is the URL of the MYOB Acumatica instance (such as https://my.acumatica.com/MyInstance). You can omit the instance name in the URL (that is, you can use https://my.acumatica.com) if the instance is installed in the root of the website.

POST /entity/auth/logout HTTP/1.1
Host: [<MYOB Acumatica instance URL>]
Accept: application/json
Content-Type: application/json

Usage Notes

If your applications failed to sign out from MYOB Acumatica and the maximum number of concurrent sessions allowed by the license is reached, there is no way to forcibly terminate all sessions of the API users. Instead, a sessions is automatically closed after a 10-minute time-out.