MCT API
MCT and MCTOnline both utilise the API for a number of functions. The MCT API is available to consume yourself but you will need an MCT account before you can use it. Please note that some API endpoints require an MCTOnline subscription (this is currently provided with all tester accounts).MCT API is based on the OpenAPI v3 standard and follows typical conventions. For more information on the specific endpoints and models you will need, please see https://www.mctoolbox.co.uk/swagger/index.html.
API Authorisation
For most API endpoints, you will be required to supply your personal API key - this can be found in your profile at https://www.MCToolbox.uk/Profile. You can additionally generate / change your API key - if you do this, any previously assigned keys will be removed and you'll need to manually update them.With few exceptions, you will also need to be authorised, including your authentication token in the header of each request. You can obtain your authorisation token with the "/MCTAuth/login" endpoint, supplying your username and password as POST parameters. A successful response will contain your authorisation token and a refresh token.
It's advisable to store the provided expiry time - from the moment of your last request, once this time time elapses you'll need to re-authorise with the API. You can do this using the refresh token with the "/MCTAuth/refresh" endpoint.