Search the Omeda Knowledge Base

< All Topics

Gift Lookup by Donor ID


This service returns all available gift information where a given Customer Id is the Donor ID and it can be filtered with optional Product Id.

General Technical Requirements

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

Base Resource URI




customerId is the internal customer id (encrypted customer id may also be used) productId (optional) is the product id.

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 a content type supported by this resource. See Supported Content Types for more details. If omitted, the default content type is application/json.

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: GET See W3C’s GET specs for details.

Lookup Gifts By Donor Id

Retrieves a record containing all gifts with the given Customer Id as the Donor 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.

Gift Recipient Elements

Element NameOptional?Data TypeDescription
FirstNamenoStringFirst name of the gift recipient.
IdnoIntegerCustomer ID of the gift recipient.
LastNamenoStringLast Name of the Gift Recipient
AddressesnoListA list of address elements. See the Postal Address Lookup by Customer ID for a list of elements.
SubscriptionsnoListA list of Subscription elements. see the Subscription Lookup By Customer Id for a list of elements
EmailsnoListA list of Email elements. see the Email Lookup By Customer Id for a list of elements.


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.

Success Example

                "Country":"UNITED STATES",
                "Street":"837 w barry ave",
                "ChangedDate":"2021-02-24 07:29:40"
               "MarketingClassDescription":"Active Qualified",
               "OriginalOrderDate":"2021-02-19 12:33:57.097",
               "ChangedDate":"2021-02-24 07:29:42",
               "OrderDate":"2021-02-19 12:34:00.0",
               "ChangedDate":"2021-02-24 07:29:40",


         "Error":"No gifts 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 gifts found for customer {customerId}.
Could not find entry in classDefinitionMap for product {productId}.
Table of Contents
Scroll to Top