Connecting Returnista

Last updated: June 16, 2026

This guide walks you through connecting your Returnista account to Engaige using an HTTP integration, enabling actions that interact with return requests, orders, consumers, and shipments.

Prerequisites

  • A Returnista account with admin access

  • Access to your Engaige dashboard with permission to manage integrations

Step 1 — Find your Returnista Account ID

  1. Log in to your Returnista dashboard

  2. Navigate to Settings

  3. Note your Account ID — this is required as part of all API call paths (format: /api/v0/account/{accountId}/...)

Step 2 — Create a Returnista API Key (Service User)

Engaige authenticates with Returnista using a non-expiring API key tied to a Service User account.

  1. In your Returnista dashboard, go to Settings → Team (or API / Developer Settings)

  2. Create a new Service User — this is a dedicated machine account for the integration

  3. Assign the appropriate permissions for the resources Engaige needs to access

  4. Once the Service User is created, generate an API key for it

  5. Copy the API key immediately and store it securely — you may not be able to retrieve it later

Step 3 — Create the HTTP Integration in Engaige

  1. Log in to your Engaige dashboard

  2. Navigate to Integrations → HTTP

  3. Click Enable

Screenshot 2026-03-05 at 15.15.45 (1).pngScreenshot 2026-03-05 at 12.09.24 (1).png
  1. Fill in the following fields:

FieldValue

Integration name

Returnista

Domain

core.returnista.com

Authentication method

Bearer Token

Bearer token

Paste the API key from Step 2

  1. Click Save

Step 4 — Create an HTTP Action linked to Returnista

  1. In Engaige, go to Actions and click Add new action

  2. Select HTTP as the action type

Screenshot 2026-03-06 at 17.43.37.pngScreenshot 2026-03-06 at 17.41.28.png
  1. Link it to the Returnista integration you just created

  2. Configure the request using your Account ID in the path:

Fetch a specific order:

  • Method: GET

  • Path template: /api/v0/account/{accountId}/return-orders?filter=purchaseOrderNumber:#{orderNumber}

  • In Action Input, you must describe the parameter orderNumber: "The e-commerce order number that the customer returned. The preprende letters of the order number must always be passed in capital letters. For example ,if a customer send their order number as "ord12345" ,you must pass in "ORD12345". If a customer is sending their order number without letters prepended, you must add the letters as capital letters "ORD". For example, if a customer is sending order number "12345", you must pass in "ORD12345"."

  1. Save the action

Fetch a specific shipment linked to an order:

  • Method: GET

  • Path template: /api/v0/account/{accountId}/return-order/#{returnId}

  • In Action Input, you must describe the parameter returnId: "The Returnista return id of the returned shipment."

  1. Save the action

For difference endpoints/actions, you can refer to Returnista's API Docs.

Step 5 — Test the Integration

  1. In the Engaige dashboard, find your Returnista action in the Actions screen. Click on the action, go to tab Test and fill a parameter if needed. You will se the response of the request you just passed.

  2. Use the Test option to verify the connection/call succeeds

Quick Reference

ItemValue

Returnista API base URL

https://core.returnista.com/api/v0

Auth header

Authorization: Bearer <api-key>

Resource path pattern

/api/v0/account/{accountId}/{resource}

API key management

Returnista Dashboard → Settings → Service Users

Security note: Use a dedicated Service User API key for Engaige. Only grant it access to the resources Engaige actually needs.