/
Configuring FreshBooks Operations

This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Configuring FreshBooks Operations

Owned by Former user (Deleted)
Last updated: Jul 08, 2015

To use the FreshBooks connector, add the <freshbooks.init>  element in your configuration before carrying out any other FreshBooks operations. This connector uses token-based authentication. For every API request that is made, you need to use HTTP basic authorization to present the unique authorization token assigned to the user. HTTP authentication traditionally takes a user name/password pair, but since we’re dealing with a single token, you’ll only use the user name field. If your HTTP library requires a password as well, just use an arbitrary string – like “X”. Click here for further reference on the authentication process.

init
<freshbooks.init>
	<arbitraryPassword>{$ctx:arbitraryPassword}</arbitraryPassword>
    <apiUrl>{$ctx:apiUrl}</apiUrl>
    <authenticationToken>{$ctx:authenticationToken}</authenticationToken>
</freshbooks.init>
Properties
  • arbitraryPassword: Optional - The arbitrary value used as the password of basic authentication.
  • apiUrl: URL of the FreshBooks API. If not provided, it is set to "https://sansu.freshbooks.com".
  • authenticationToken: The authentication token for the FreshBooks account, which refers to the user name in basic authentication.

Now that you have connected to FreshBooks, use the information in the following topics to perform various operations with the connector.

Multipart/form-data cannot be processed inside the ESB. Therefore, the ESB should be in a content-unaware status. To achieve this, configure a pass-through proxy, and then build the message from the client end and send it to the proxy.