PEAK Create Expense icon

PEAK Create Expense

Send JSON payload to create expense via PEAK API

PEAK Create Expense

AI-generated

Summary

Sends a JSON payload to the PEAK API to create an expense, authenticating with credentials and signing requests using a timestamp and HMAC.

Inputs

  • serverEnvironment (required) — Select the API environment. Production URLs the API endpoint to api.peakaccount.com; UAT uses peakengineapidev.azurewebsites.net.
  • Body (required) — Raw JSON object defining the expense. Must be valid JSON; includes merchantId, issueDate, and items array by default.
  • clientTokenOverride — Optional client token to override the credential value. Useful if the token refreshes every 24 hours.

Output shape

A single item for each input item containing success status, HTTP status code, the response data, and the request headers.

If the configuration contains multiple items, the node processes them sequentially. If continue on fail is enabled, errors are returned as items with an error field rather than failing the workflow.

Examples

Example 1: Create a single expense in production using mapped data.

Server Environment: Production, JSON Body: {"merchantId": "123", "issueDate": "2025-10-16", "items": [{"name": "Lunch", "cost": 25}]}

Example 2: Create an expense in UAT with a manually provided client token.

Server Environment: UAT, Client Token Override: provided-token, JSON Body: mapped from previous node

Links

Discussion