Search the Omeda Knowledge Base

< All Topics

Customer Lookup By PostalAddressId


This API provides the ability look up customers using their Postal Address Id (this is the ID on the magazine mailing labels).  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.

  • If the customer has been merged into another customer or deactivated an error message will be returned. (Please see failure section for more details)

General Technical Requirements

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

Base Resource URI



brandAbbreviation is the abbreviation for the brand postaladdressId is the internal postal address id. This is typically what a magazine subscriber would find on their mailing label.

HTTP Headers

The HTTP header must contain the following elements: 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

content type is 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 Postal Address Id

Retrieves a single 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)
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"


Standard Customer Error Message
         "Error":"Postal Address Id 123456 was not found."
Merged Customer Error Message
         "Error":"Customer id 22 is valid but not active. Please use 99999."
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.

Postal Address Id {postaladdressId} was not found.
Customer id {customerId} is valid but not active. Please use {mergedIntoCustomerId}.
OmedaCustomerId {customerId} is pending deactivation. Please try again later.
Table of Contents
Scroll to Top