Make App

The Surense app for Make gives you a module for every operation in the Surense API, so you can build scenarios without writing HTTP requests yourself.

What's included

• 177 modules, one per documented API operation: 140 actions (create, get, update, delete, export…) and 37 searches.
• Make an API Call: a universal module for any Surense endpoint, using the same connection.
• Dropdowns for statuses, types, sources, classes, tags, users, supervisors, document types and providers, so you pick values by name instead of typing IDs.
• Automatic paging: search modules fetch every page for you. Use the Limit field to cap the number of results.

Modules are grouped by area:

Create a connection

The app connects with OAuth 2.0 client credentials. You need a Surense API Client ID and Client Secret.

1. In a Make scenario, add any Surense module.
2. Next to Connection, click Add.
3. Enter your Client ID and Client Secret, then click Save.

Make requests an access token from https://api.surense.com/oauth/token and renews it automatically when it expires. When you save, Make checks the connection by calling GET /user/info.

The modules can only do what your API client is allowed to do. If a module returns a permission error, check that the client has the scope listed for that operation in the API reference (for example global:export for exports).

Errors

Failed requests show the HTTP status code followed by the Surense error message, in the form [status] message. You can handle them with Make's error handlers (Resume, Ignore, Break…).

Good to know

• File uploads: uploading a file's content isn't supported yet. The legacy multipart upload (POST /documents/upload) has no module.
• Delete modules return success: true when the delete succeeds.
• Some operations have no documented response format; their modules return the raw response body.
• For ready-made scenarios, see Make - Examples.