Waiting for engine...
Skip to main content

Introduction

The Audit Log Staging APIs provides the ability to download audit logs.

To execute the Audit Log Staging Service APIs, you must provide an authentication token generated from the Boomi Enterprise Platform. Learn more about the token authentication, sample requests and responses, and the different error codes of these APIs.

note

The Audit Log Staging APIs use a Boomi-JWT authentication, which is different from the basic-auth authentication of the Boomi Enterprise Platform APIs.

Interactive API Testing​

Import the Boomi AuditLog Staging API collection into Postman to test endpoints, view request examples, and accelerate your integration development.

For more information about Postman collections, forking, and making your first API call, refer to the Working with Boomi APIs on Postman page.

Run In Postman

API Errors​

400 (Bad Request): Input parameters are invalid.

401 (Unauthorized): User access tokens are invalid or expired.

404 (Not Found): The specified url/request could not be found.

403 (Forbidden)

405 (Method Not Allowed): The request method is not supported.

409 (Conflict): A request with the same accountId and date range already exists.

500 (Internal Server Error): Unexpected server issues.

JWT authentication tokens​

These APIs require JWT authentication. Include your JWT bearer token in the Authorization header of each request.

To generate a JWT token, you must use HTTP Basic authentication and provide your Boomi Enterprise Platform account username and password in a GET request to the Platform API.

Send a GET request to:

  • US: https://api.boomi.com/auth/jwt/generate/{accountId}

  • GB: https://api.platform.gb.boomi.com/auth/jwt/generate/{accountId}

Where {accountId} is the ID of the authenticating account for the request. You can obtain your Platform account information in Settings > User Information > Account Information.

note

JWT tokens expire after 5 minutes. If you make a request with an expired token, you will receive a 401 error.

On this Page