Hybrid Flow: Obtaining of an Access Token and ID Token from the Token Endpoint

To obtain an ID token and access token from the token endpoint, a client application that implements the Hybrid flow connects to the token endpoint of MYOB Acumatica with the POST method. For details on the request and the response, see the following sections.

HTTP Method and URL

The client application connects to the token endpoint of MYOB Acumatica with the POST method. The client application can use one of the following options for the URL:

If the client application supports OpenID Connect Discovery, the client application can use the discovery endpoint address, as shown in the following code.
```
https://<MYOB Acumatica instance URL>/identity/.well-known/openid-configuration
```
Note:
We recommend that the client application use the discovery endpoint address, which eliminates the need to change the application if the target endpoint address changes.
The client application can directly use the token endpoint address, as shown in the following code.
```
https://<MYOB Acumatica instance URL>/identity/connect/token
```

HTTP Header

You use the following HTTP header.


Key	Value
`Content-Type`	`application/x-www-form-urlencoded`

Request Body

You specify the following parameters in the request body.


Parameter	Description
grant_type	The type of the flow, which must be set to authorization_code for the Hybrid flow.
client_id	The client ID that was assigned to the client application during the registration of the application in MYOB Acumatica. The client ID must have the format in which the ID was generated during the registration of the application. That is, the client ID must include an auto-generated string and the ID of the tenant, such as 88358B02-A48D-A50E-F710-39C1636C30F6@MyTenant. The client application will have access to the data of the tenant specified in the client ID.
code	The authorization code that the client application has received from the authorization endpoint.
client_secret	For a client application that uses a shared secret, the value of the secret that was created for the client application during the registration of the application in MYOB Acumatica.
client_assertion_type	For a client application that uses JSON Web Token (JWT) bearer tokens, the client assertion type, which must be set to urn:ietf:params:oauth:client-assertion-type:jwt-bearer.
client_assertion	For a client application that uses JSON Web Token (JWT) bearer tokens, a single JWT.
redirect_uri	The URI in the client application to which the response to the request should be sent. The URI must exactly match one of the values specified for the application in the Redirect URI column on the Redirect URIs tab of the Connected Applications (SM303010) form.

Response

MYOB Acumatica verifies the provided application credentials and issues an access token, an ID token, and a refresh token if they have been requested by the application. The client application should provide the access token with each data request to MYOB Acumatica.

A successful response includes the following parameters in the response body.


Parameter	Description
token_type	The type of the access token, which is Bearer. The parameter is returned only if the api scope was granted.
access_token	The access token. The parameter is returned only if the api scope was granted.
expires_in	The period of time (in seconds) during which the access token is valid. The parameter is returned only if the api scope was granted.
scope	The scope for which the access token and ID token are provided. The returning of this parameter is optional.
refresh_token	The refresh token. The parameter is returned only if the offline_access scope was granted.
id_token	The ID token associated with the authenticated session. The ID token contains three parts, which are separated by periods. The parts are Base64 encoded. The second part contains the claims to which the user granted access. For details on the ID token structure, see https://openid.net/specs/openid-connect-core-1_0.html#IDToken and https://www.rfc-editor.org/rfc/rfc7519.html. We recommend that you use the existing standard libraries for parsing the tokens. The parameter is returned only if the openid scope was granted.

Example

The following example shows a request for access token with a shared secret provided with the request. (Line breaks are for display purposes only.)

POST /identity/connect/token HTTP/1.1
Host: https://localhost/AcumaticaDB
Content-Type: application/x-www-form-urlencoded

grant_type=authorization_code
&client_id=C07F7B7A-8947-3C56-2B27-A46CA1F8EF8F@U100
&client_secret=sJli5nNartFBX4Ckzpb68g
&code=z0ExIPH9pAdJSc5nDVakHwYW2jnt91B9oyoZQvdp3cQ
&scope=openid%20email%20profile%20api%20offline_access
&redirect_uri=https://localhost

A successful response has the body shown in the following example.

{
    "id_token": "eyJ...Z5A",
    "access_token": "9zx2acU03l0ORLHfqwdCPxFHWJMzlLDqrOfJjlZcb_I",
    "expires_in": 3600,
    "token_type": "Bearer",
    "refresh_token": "sbUAHaA7xST3vnvlsanRh3M5EWNmAW_fu6CX16ZEQqM",
    "scope": "openid email profile api offline_access"
}