MyFMS APIv3 Authentication
Preface
This guide provides information about the API3
authentication.
The requirement for API3 authentication is that you have
access to a MyFMS account.
In this document we use an application Postman for Windows.
You can find Postman on the following webpage. You can
also access Postman through your web browser.
We work with an OpenAPI / Swagger. More information can be
found on the website that can be found here.
We can help you with the implementation. We charge two days
of consultation for this. Send an email to support@myfms.nl for
more information or questions.
Creating a request
To get the Accounts Endpoint go to the following webpage:
The response should look something like this:
Refresh this every now and then as this can change. Advise
Max TTL 24 hours
Requesting the the endpoints with the response above shows
example below
Use the token endpoint to request an access token.
- In Postman create a new request
- as Request method we select: Post
- Fill in the token endpoint received from openid-configuration: https://accounts.myfms.com/connect/token
- as Body use "x-www-form-urlencoded"
In the Body use "x-www-form-urlencoded"
Requesting an access-token with user credentials
use following parameters
KEY | VALUE |
client_id | MyFMS.Api.V3 |
grant_type | password |
username | your username |
password | your password |
Click Send and
the result should look like this:
Use the access-token in the Calls to The API as Bearer token
in the Authorization Header
The refresh-token is for one-time-use only and expires after
30 days!
The access-token expires after 1 hour (3600 sec.).
The
refresh-token is used to request a new access-token without using the username
and password again.
Requesting
an accesstoken with a refreshtoken
use following parameters
KEY | VALUE |
client_id | MyFMS.Api.V3 |
grant_type | password |
refresh_token | refresh-token received from previous authentication request |
Click Send and
the result should look like this: