Entity & Metadata

The entity structure and the metadata you can send along with the API request body.

Understand the API entity structure and how to send metadata using the notes object parameter in the API request body.

Every API response contains entities shared across different endpoints. There are some common attributes for every entity.


string Indicates the type of the entity.


integer A unique identifier of the entity.

In an entity, the attributes can be used to make entity-specific API calls. For example, you can fetch the payment ID from an order.paid webhook and use it to initiate a refund for that payment.

Curlec APIs also support returning multiple entities for a single request. This response also has another entity collection. For the collection entity, the following parameters are common.


string Indicates the type of the entity. For example, collection.


integer Indicates the number of items are returned. For example, 2.


array The list of entities.

The majority of the entities allow the notes object to store additional information and preserve data relevant to your integration. Curlec does not use it for any operational purposes.

The notes object is a set of key-value pairs that can be used to store additional information about the entity. It can hold a maximum of 15 key-value pairs, each 256 characters long (maximum).

You can store the notes related to:

  • Billing or shipping address of the initiated payment.
  • Reference ID generated for an order.

Was this page helpful?