Skip to main content

Migrating from api.dockmaster.com to api.dmeapi.com

Below is a summarized set of steps for third-party integrators, based on the Multi-Tenant API guide.

Environment URLs​

Testing/Sandbox​

Production​

Migration Steps​

1. Authenticate via the Auth API​

Request an access token and refresh token using provided credentials.

Endpoint: https://auth.dmeapi.dev/token (for sandbox)

The response will contain:

  • An auth token
  • A refresh token
  • A list of available system connections (with SystemId values)

2. Select the Target System (Tenant)​

Each API request must include the X-DM_SYSTEM_ID header.

The value must match one of the SystemId values returned in the token response.

3. Call the DockMaster API​

To call the DockMaster API, you must include the following headers on every request:

  • Authorization: The value should be Bearer followed by a space and the auth token from the Auth API
    • Example: Authorization: Bearer <your_auth_token>
  • X-DM_SYSTEM_ID: The value should be one of the SystemId values from the token response

Use the appropriate API base URL:

  • Sandbox: https://api.dmeapi.dev
  • Production: https://api.dmeapi.com

4. Handle Token Refresh​

Implement token refresh logic using the refresh endpoint.

Endpoint: https://api.dmeapi.dev/token/refresh (for sandbox)

To obtain a new auth token using the refresh token, you must pass both:

  • The old or expired auth token
  • The refresh token

Both tokens are required to obtain a new set of tokens.

5. Testing​

  • Validate integration in the sandbox environment before moving to production.
  • Use the Swagger documentation pages to explore available endpoints and test API calls.
  • Ensure correct handling of multi-tenant context, especially if customers manage multiple systems.