Exact Online

​

Extra information

System documentation: Exact Online API Reference

​

Connector package documentation

​

Table of Contents

• 1. Setting up HTTP Client Exact Online
  • 1.1 Steps
• 2. Subscribing to entities from Exact Online
  • 2.1 Steps
  • 2.2 General concept
• 3. Publishing entity to Exact Online
  • 3.1 Steps
  • 3.2 General concept

​

1. Setting up HTTP Client Exact Online

1.1 Steps

1. In the Alumio Dashboard, go to Clients -> HTTP Clients. Create a new HTTP Client and select “Exact Online HTTP Client” as the HTTP Client.
2. Fill in the Base URI, Client ID, Client Secret, and Scopes (Optional). (For more information, see Exact Online Reference)
3. Click on “Grant access to Exact Online” to get the Key.
4. You can optionally enable logging of request to get the log of the authentication.
5. Save the HTTP Client for use.

​

2. Subscribing to Entities from Exact Online

2.1 Steps

1. Go to Connections -> Incoming and create a new incoming configuration and select “Exact Online Subscriber” as the subscriber.
2. Select the entity you want to subscribe to from Exact Online.
3. Add any request parameters needed to subscribe to the entity.
4. You can optionally add a transformer to transform the request parameters into something you will request from Exact Online.
5. You can also optionally enable pagination to allow Alumio fetches paginated entities.
6. Select the Exact Online HTTP Client to use.

2.2 General Concept We follow Exact Online documentation on building this connector, so you can easily use the connector based on Exact Online API Reference. Entity The entity you want to subscribe to Exact Online. Please refer to the entities from Exact Online API Reference page. Request Parameters These are the parameters you can provide to get the needed entity based on the Exact Online API Reference. Please look at the example below on how to fill path field when subscribing “AccountOwners” entity. Based on the documentation, we can see that the end point require “division” as a path. That is why we set the “division” inside the path key in the Request Parameters.

• Path is the path parameter of the url. For example the {channelId}.
• Query is defined set of parameters attached to the end of a url.
  Example: www.url.com?type=true&start=0

Alumio will then make a request to Exact Online with the URL /api/v1/3389687/accountancy/AccountOwners HTTP Client The HTTP Client configuration you will use to access Exact Online.

​

3. Publishing Entity to Exact Online

3.1 Steps

1. Go to Connections -> Outgoing, create a new outgoing configuration and select “Exact Online Publisher” as the publisher.
2. Select the Action that you want the publisher to perform with the data.
3. Select the Exact Online entity you want the data to be published to.
4. You can optionally add any path data to the request on the key path.
5. You can optionally add any query data to the request on the key query.
6. You can optionally add any payload data to the request on the key payload.
7. Select the HTTP Client to use.

3.2 General Concept Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration), though you can also add or modify payload using the Request Transformer. Action Currently, we support Create (HTTP POST method), Update (HTTP PUT method), Patch (HTTP PATCH method), and Delete (HTTP DELETE method) on submitting data to Exact Online. Entity We support publishing to most Exact Online endpoints. Please refer to Exact Online API Reference page. For example, we want to create owner of an account. Please select “Create” as the Action and “AccountOwners” as the entity of the publisher. Based on the documentation, we can see that the end point require “division” as a path. That is why we set the “division” inside the path key in the Data. We also need to provide the body of the request, add it inside the payload key in the data. Alumio will send an API request to Exact Online with URL /api/v1/3389687/accountancy/AccountOwners

• Path is the path parameter of the url. For example the {id}.
• Query is defined set of parameters attached to the end of a url.
  Example: www.url.com?type=true&start=0
• Payload is the data contained within a request.

HTTP Client The HTTP Client configuration you will use to access Exact Online.