Skip to main content

Authentication

All Flex Forward API endpoints require authentication via two headers: x-rr-apikey and x-rr-apitoken.

Getting your API credentials

API credentials are managed in the Return Helper User Portal. You need a Return Helper user account — the same login you use for the Flex Forward Portal. Follow the steps in the Return Helper API authentication guide to locate or generate your credentials under Settings → Signing Key and API Token. You need both values shown there: The same API key and API token authenticate both the Flex Forward API and the Return Helper User API:
Every authenticated Flex Forward request must include both headers. Requests that omit either header are rejected with HTTP 401.
Keep your API token and API key secret. Do not share them in client-side code, public repositories, or insecure channels.

How access works

1

Sign in to the User Portal

Log in to the Return Helper User Portal with the same account you use for the Flex Forward Portal.
2

Get your credentials

Go to Settings → Signing Key and API Token, or follow the Authentication instructions on the Return Helper API docs. Copy both the API key and the API token.
3

Authenticate Flex Forward requests

Include both x-rr-apikey and x-rr-apitoken on every request (see below). The same pair authenticates Return Helper User API calls.
4

Need help?

For account access, portal login issues, or other enquiries, contact [email protected].

Making authenticated requests

Include both headers on every request:

Error responses

If either credential is missing or invalid, the API returns a 401 Unauthorized response:
If the credentials are valid but the caller does not have access to the requested resource, the API returns a 403 Forbidden response:

Credential best practices

  • Credentials are created, regenerated and revoked by you in the User Portal under Settings → Signing Key and API Token. Flex Forward does not rotate or expire them on your behalf; decide your own rotation policy and regenerate when you need to
  • Use separate credentials for development and production environments
  • Store credentials in environment variables or a secrets manager — never hard-code them