Laurel

This document outlines the current process for ingesting Intapp Walls data within Laurel’s Aderant and 3E data pipelines.

___________________________________________________________

To enable Walls data ingestion, the following are required:

- A CSV file containing <code>Email</code>, <code>Timekeeper ID</code>, and <code>Walls</code> fields is needed for manual import of users during the first run.

- A service account that can authenticate against the Walls service endpoint is required.
- Service endpoint: <code>http://&lt;baseurl&gt;/APIService/InternalAPIService.svc</code> 

1. <b>Manual Data Import:</b>
   - A CSV file containing <code>Email</code>, <code>Timekeeper ID</code>, and <code>Walls</code> fields is needed for manual import of users during the first run.
2. <b>Service Account Authentication:</b>
   - A service account that can authenticate against the Walls service endpoint is required.
   - Service endpoint: <code>http://&lt;baseurl&gt;/APIService/InternalAPIService.svc</code> 

Send the above requirements to your account team, and they will turn on Walls integration.

Our integration will talk over WSDL and SOAP to the service endpoint you provide us.

We currently support Walls with Aderant and Elite 3E.

For additional information or support, please refer to your Laurel deployment guide or contact our support team.

Integrating Intapp Walls with Laurel

Find answers and get help from Intercom Support and Community Experts

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Title

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Requirements

Setup