API & Integrations
      Back to home
      1. Help Center
      2. Technical
      3. API & Integrations

      Using Multi-Account API Tokens to Integrate Multiple Prokeep Accounts with a Single Endpoint

      Overview

      The Multi-Account API Token feature allows organizations with multiple Prokeep accounts to send messages using a single API integration. This is especially useful for companies that have a centralized ERP or business system—like Epicor Eclipse or Innovo—but operate many Prokeep accounts across branches or regions.

      Instead of building separate integrations for each account, you can send order delivery notifications or other messages through one endpoint using a single set of credentials. Prokeep handles routing based on the from number in each request.

      Who This Is For

      This feature is designed for customers who:

      • Operate multiple Prokeep accounts (e.g. by region, brand or acquisition)

      • Have a centralized ERP or messaging system

      • Want to send messages (such as order notifications) across all locations without merging accounts

      • Need a scalable, low-maintenance integration

      How It Works

      • Prokeep provides a single API username and password (Basic Auth)

      • Use the standard POST /messages endpoint

      • Prokeep automatically determines the account based on the from number in the payload

      • No need to manage multiple tokens or include account IDs in requests

      Example Endpoint

      If your login URL is https://yourorg.prokeep.com, your Messaging API endpoint will be:
      https://yourorg.prokeep.com/rest/v1/messages

      This single endpoint works for all of your linked Prokeep accounts — for example, northbranch.prokeep.com, southbranch.prokeep.com, and hq.prokeep.com. Even though these accounts have different subdomains, you’ll use the same endpoint and credentials for all of them.

      As long as the from number in the request is tied to a valid conversational line in one of those accounts, Prokeep will automatically route the message to the correct account. No need to switch subdomains, change tokens, or include account IDs.

      Authentication

      • Uses Basic Authentication (username and password)

      • Credentials do not expire unless manually rotated

        • Prokeep can rotate credentials upon request

      Using the Messaging API

      The structure of your API requests remains the same as documented in the Prokeep Messaging API.

      • The from number must be a valid conversational line tied to a group in one of the linked accounts

      • Prokeep handles message routing — no account ID required

      • Only the POST /messages endpoint is supported

      For full request structure and response examples, refer to the Prokeep Messaging API documentation.

      Example Request

      curl -u 'your_username:your_password' \
        --request POST 'https://yourorg.prokeep.com/rest/v1/messages' \
        --header 'Content-Type: application/json' \
        --data-raw '{
          "from": "+15556667777",
          "to": "+15557776666",
          "text": "Your order is out for delivery."
        }'

      Getting Started

      To request a Multi-Account API Token:

      1. Contact your Prokeep Customer Success Manager (CSM)

      2. Request must come from an admin on one of the accounts

      3. Provide a list of accounts to be linked to the token

      Your CSM and Technical Account Manager (TAM) will provide:

      • Your API endpoint (based on one of your account subdomains)

      • Your Basic Auth credentials (username and password)

      Important Notes

      • This feature currently supports only the POST /messages endpoint

      • In-app API Logs will not show activity from Multi-Account Tokens

      • Customers do not need to create an API key inside the Prokeep application