Skip to content
More support
Contact Us
  • There are no suggestions because the search field is empty.

How do I use the SILQ API

SILQ allows API access for certain plans, and supports a full OAuth2 token flow that provides a token that can then be used as with subsequent API calls.

Warning: Sensitive Information Exposure Risk

Using this API may result in unintended disclosure of sensitive personally identifiable information (PII), including data that is subject to legal professional privilege. Any information transmitted, logged, or processed through the API could be exposed to third parties, external systems, or public domains if not handled with strict security controls. This includes names, addresses, identity documents, financial details, or any privileged client information.

Once transmitted, you may lose control over how the data is stored, replicated, or accessed, and it may no longer meet your regulatory, confidentiality, or privilege obligations. By proceeding, you acknowledge that you are responsible for ensuring no sensitive or privileged information is sent through the API unless you have verified that your usage complies with all legal, ethical, and professional requirements.

Using our API in some AI systems can be particularly dangerous, so we caution you to take care in these environments.

To integrate with SILQ, what you need to do is the following.

API access is only available on the Barrister Expert and Solicitor Expert plans

    • If you are a third party developer and do not have a SILQ account already, go to https://online.silq.com.au/#/sign-up and create an account following that process. This will create a free 14 days trial of the software, but you can apply for that to be extended if need be.
    • Once you have an account go to https://api.silq.online/openapi/index.html#/ for details on our API.
    • You will need to register an app in our OAuth2 system 
      • You can either use the oauth2/apps endpoint - We recommend you use a tool such as Postman to execute the request top register the app.
      • Or, use the SILQ UI to register the app. Go to System Settings -> API Access (available very soon)
      • This only needs to be done once.
      • Make sure your store you client id and secret as the secret will only be sent to you when the app is created, but you can generate a new secret by updating the app with the REGENERATECLIENTSECRET:true parameter.
      • You can register up to 3 redirect URLs.
      • It will return also an APIKEY (ApiGatewayApiKeyId) which will be needed to be passed to the API as a header (X-API-KEY) in the near future.
    • Once the app is created you can then use the oauth2/token and oauth2/authorise endpoints to acquire an OAuth2 token using a standard OAuth2 flow. That token can then be used with the API. Tokens expire after 1 hour and after that you will need to refresh the token using the RefreshToken to acquire a new token.
    • When calling an API you will need to provide the OAuth2 token as an Authorization header (and soon you will need to provide the X-API-KEY header as well) Any token that you create will be tied to the X-API-Key for your app so will not work without it.
    • Currently we have only documented a limited number of end-points. If there are other features of SILQ that you would like to have API access to, please contact support@silq.com.au

 

FAQ:

    • What is the correct production base URL we should use for API calls.
      • https://api.silq.online
    • What scopes should be requested for read-only access to matters, contacts, documents/cloud storage, work items/WIP, invoices?
    • Are there costs to use the API?
      • Potentially yes, your subscription will include a certain number of API calls, but any additional API calls over this amount will be charged on a usage basis. Please contact SILQ Sales  sales@silq.com.au for more details.
    • Does the API support reading a matter's trust balance and trust ledger transactions?
      • Yes
    • Does the API support creating trust receipts?
      • Not at this stage
    • Does the API support creating Trust To Office transfers against a specific invoice, including bank date and bank reference fields?
      • Not at this stage
    • Does the API support creating/updating WIP?
      • Yes
    • Does the API support generating invoices from WIP?
      • Not at this stage
    • Does the API supports recording invoice receipts/payments?
      • Not at this stage
    • Is invoice register data available, including invoice status, paid amount, outstanding amount and any linked trust/accounting fields.
      • Yes, but not documented yet
    • Is validate-only or dry-run actions are available for accounting/trust writes before saving?
      • Yes, most APIs that support writing data allow a parameter “ValidateOnly”. This will return validations errors and warnings without processing the request.
    • Is audit-log readback is available?
      • Not at this stage
    • Is there a sandbox/test tenant is available for testing before using anything against live trust/accounting data.
      • We suggest you create a free trial database for this purpose and then ask our support team to upgrade the trial database to tier 3.