Metadata
Learn how to store arbitrary custom metadata in various objects in Monite.
Overview
Payables, Receivables, Entity, Counterpart, and Counterpart bank account objects can have arbitrary metadata associated with them. Monite API Partners can use metadata to store additional structured information about these objects, such as the object IDs from other systems.
The way to work with metadata varies depending on the object type. Refer to the corresponding section below:
Entity and counterpart metadata
The metadata is not part of the Entity
and Counterpart
objects themselves. Instead, it is accessed via the /partner_metadata
subresource of the corresponding resources:
Use the HTTP PUT method to set the metadata, and GET to read it.
Metadata format
The <resource>/partner_metadata
endpoint accepts and returns the metadata in the following format, where metadata
can be an arbitrary JSON object up to 2000 bytes in size:
Set metadata
Use PUT <resource>/partner_metadata
to add metadata or replace existing metadata for a specific entity or counterpart. For example:
A 200 OK
response means the metadata was successfully saved. If the metadata exceeds the 2 KB limit, a 422
response is returned.
Get metadata
Use GET <resource>/partner_metadata
to get existing metadata for a specific entity or counterpart. For example:
If there is no metadata associated with the specified entity or counterpart, the metadata
field in the response is an empty object {}
.
Partially update metadata
If you need to add, modify, or delete individual fields within a metadata object, you can use this approach:
- Call
GET <resource>/partner_metadata
to read existing metadata. - Modify the returned object as needed.
- Call
PUT <resource>/partner_metadata
to save the modified metadata.
Delete metadata
To delete the metadata associated with a specific entity or counterpart, you can call PUT <resource>/partner_metadata
and pass an empty object {}
as the metadata
value:
Payables, receivables, and counterpart bank account metadata
Metadata format
Payable
, Receivable
, and Counterpart Bank Account
objects have the partner_metadata
field to store partner-provided metadata. The value can be an arbitrary JSON object up to 2000 bytes in size:
If there is no metadata associated with a specific payable, receivable, or bank account, the partner_metadata
field returns an empty object—{}
.
Set metadata
When creating a payable, receivable, or counterpart bank account, you can provide the metadata by using the partner_metadata
field directly in the request object as shown:
In case of already existing payables, receivables, or counterpart bank accounts, you can add metadata by sending a PATCH
request to the respective endpoint and including the partner_metadata
field as shown:
Get metadata
To retrieve the metadata of a payable, receivable, or counterpart bank account, send a GET
request to the corresponding resource.
The following snippet demonstrates a response from the GET /payables
request, which includes the partner_metadata
of each payable:
Partially update metadata
To add, modify, or delete individual fields within the metadata of a Payable
, Receivable
, or Counterpart Bank Account
object, you can use this approach:
- Retrieve the object by using the corresponding
GET
request (such asGET /payables/{payable_id}
). - Extract the
partner_metadata
response field to get existing metadata. - Modify the
partner_metadata
value as needed. - Send a
PATCH
request to update the object and provide the updatedpartner_metadata
value in the request.
Delete metadata
To delete existing metadata from a Payable
, Receivable
or Counterpart Bank Account
object, send a PATCH
request to the corresponding endpoint and set partner_metadata
to an empty object {}
as shown: