Search the Omeda Knowledge Base

< All Topics

External ID Lookup By Customer Id


This API provides the ability look up a Customer’s External Ids by the Customer Id.

General Technical Requirements

The following technical requirements apply to all requests for this API.

Base Resource URI



brandAbbreviation is the abbreviation for the brand customerId is the internal customer id (encrypted customer id may also be used)

HTTP Headers

The HTTP header must contain the following element: x-omeda-appid a unique id provided to you by Omeda to access your data. The request will fail without a valid id.

Content Type

The content type is application/json. JSON application/json

JSON is the preferred data exchange format, because it is lightweight and, in most cases, faster to process and utilizes less bandwidth. There are many available open-source JSON libraries available. See for details.

Supported HTTP Methods

There is one HTTP method supported:

  1. GET : See W3C’s GET specs for details.

Lookup External Ids By Customer Id

Retrieves all available External IDs stored for a given customer id.

Field Definition

The following tables describe the hierarchical data elements.

In addition to the below elements, a SubmissionId element will also be returned with all responses. This is a unique identifier for the web services response. It can be used to cross-reference the response in Omeda’s database.

External Ids Elements

Element NameDescription
CustomerElement containing an HTTP reference to the owning customer resource.
ExternalIdsEach ExternalId element contains Id and Namespace information for each external ID that is stored.

External Id Elements

Element NameAlways Returned…Data TypeDescription
IdYesLongThe external identifier
NamespaceYesStringThis is the acronym used to differentiate the different kinds of external ids. For example, RDRNUM for the Omeda Legacy Id.


HTTP Response Codes

200 OKThe request has succeeded. See Example Response below.
403 ForbiddenTypically, this error occurs when the credentials are erroneous. Potentially, an incorrect x-omeda-appid.
404 Not FoundTypically, this error occurs with a malformed URL or the resource that is searched for is not found.
500 Internal Server ErrorIn the rare case that there is a server-side problem, this response will be returned. This generally indicates a problem of a more serious nature, and submitting additional requests may not be advisable. Please contact your Omeda Account Representative if the issue continues.


   "SubmissionId" : "24B9BF6F-0677-462B-942A-D87EEBD10F77"


         "Error":"No External Id found for customer 12345."
Possible Error Messages

In the event of an error, an error response will be returned. Here are some of the possible responses you might receive.

No External Id found for customer {customerId}.
Error looking up customer by customer id {customerId} for brand {brandId}.
Table of Contents
Scroll to Top