Search the Omeda Knowledge Base

< All Topics

Customer Lookup By External ID


This API provides the ability look up a Customer by the External Customer Id.   The response will include Customer Id and various links to look up additional Customer information such as Demographics, Addresses, etc for a single Customer record.

General Technical Requirements

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

Base Resource URI


brandAbbreviation is the abbreviation for the brand externalCustomerId is the client’s customer ID externalCustomerIdNamespace is the type of ID you would like to lookup. Please contact your Omeda Account Representative for what code to use here.

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 Customer By External ID

Retrieves a single active customer record containing all available name, contact, and demographic information about the customer.

Field Definition

The following table describes the data elements present on the response from the API.

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.

Customer Elements

Element NameAlways Returned…Data TypeDescription
IdYesIntegerinternal id (for use on certain databases)
EncryptedCustomerIdNoStringThe Encrypted Customer Id for the customer
CustomerYesLinka link reference to the customer data as a resource.
AddressesYesLinka link reference to the address data as a resource.
PhonesYesLinka link reference to the phone data as a resource.
EmailAddressesYesLinka link reference to the email data as a resource.
CustomerDemographicsYesLinka link reference to the customer demographic data as a resource.
SubscriptionsYesLinka link reference to the subscription data as a resource.


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.


   "Id" : 12345,
   "Customer" :             "*",  
   "Addresses" :            "*",  
   "Phones" :               "*",
   "EmailAddresses" :       "*",
   "CustomerDemographics" : "*",
   "Subscriptions" :        "*",
   "SubmissionId" : "24B9BF6F-0677-462B-942A-D87EEBD10F77"


         "Error":"External Customer Id 12345 Not Found for the External Customer Id Namespace RDRNUM"
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.

External Customer Id {externalCustomerId} not found for the External Customer Id Namespace {externalCustomerIdNamespace}.
Table of Contents
Scroll to Top