API Explorer 891 endpoints

Get parcel_on_chain List

GET /obp/dynamic-entity/parcel_on_chain

OBPv4.0.0-dynamicEntity_getparcel_on_chainList_ Roles: CanGetDynamicEntityRecord_parcel_on_chain(per bank) _Parcel_on_chainDynamic-EntityDynamic

Get parcel_on_chain List.

For data from the block chain about about parcels. This Dynamic Entity is part of OGCR.

Property List:

  • parcel_id: Links to the parcel dynamic entity. The on-chain NFT is keyed by this id.
  • token_id: CarbonProjectNFT token id minted for this parcel.
  • carbon_amount: Carbon amount stored on-chain for this token.
  • project_type: Project type as stored on-chain.
  • methodology: Methodology as stored on-chain.
  • vintage: Vintage year as stored on-chain.
  • minted_at: On-chain block timestamp (mintedAt) from projectData, unix seconds.
  • owner_address: Current owner of the NFT (operator OGCR wallet address).
  • token_uri: tokenURI of the NFT (ERC721 metadata data-URI).
  • contract_address: CarbonProjectNFT contract address the token was read from.
  • chain_id: EVM chain id (OGCR chain = 2025).
  • tx_hash: Mint transaction hash (from the CarbonProjectMinted
  • block_number: Block number the mint was included in.

MethodRouting settings example:

<details>

{
  "is_bank_id_exact_match":false,
  "method_name":"dynamicEntityProcess",
  "connector_name":"rest_vMar2019",
  "bank_id_pattern":".*",
  "parameters":[
    {
        "key":"entityName",
        "value":"parcel_on_chain"
    }
    {
        "key":"url",
        "value":"http://mydomain.com/xxx"
    }
  ]
}

</details>

User Authentication is Required. The User must be logged in. The Application must also be authenticated.

Filtering, sorting and pagination on the list endpoint:

(no fields on this entity are declared indexed, so only the legacy bare-parameter filter below is available.)

  • Filter: ?obp_filter[FIELD]=OP:VALUE. Operators: eq, ne, in, lt, gt, le, ge, between, like, is_null, not_set. in / between take comma-separated values; is_null / not_set take no value. Repeat the same key to AND several constraints on one field. e.g. ?obp_filter[status]=eq:active&obp_filter[amount]=between:10,100 or ?obp_filter[closed_date]=not_set
  • Legacy filter (still supported): bare field parameters, e.g. ?name=James%20Brown&number=123.456&number=11.11 filters by name == "James Brown" && (number == 123.456 || number == 11.11).
  • Sort: ?obp_sort_by=FIELD[,FIELD2]&obp_sort_direction=ASC|DESC.
  • Paginate: ?obp_limit=20&obp_offset=40.

Filtering, sorting, pagination and is_null / not_set work on every deployment (no special backend required).

One-hop joins (EXISTS / NOT EXISTS) — filter this entity by a condition on a related entity linked through a declared reference: field:

  • ?obp_exists[RelatedEntity] — keep rows that have at least one related RelatedEntity.
  • ?obp_exists[RelatedEntity]=filter[FIELD]=eq:VALUE — ...that have at least one matching the predicate.
  • ?obp_not_exists[RelatedEntity] — keep rows with NO related RelatedEntity at all.
  • ?obp_not_exists[RelatedEntity]=filter[FIELD]=eq:VALUE — ...with no related RelatedEntity matching the predicate (this includes rows that have no related RelatedEntity).
  • If two entities are linked by more than one reference, disambiguate the edge with via:, e.g. ?obp_exists[RelatedEntity]=via:buyer_ref;filter[status]=eq:signed.

The nested filter[...] reuses the operator grammar above. Mind the distinction: obp_not_exists[X]=filter[flag]=eq:true (no related X with flag=true — includes rows with no X) is not the same as obp_exists[X]=filter[flag]=ne:true (has a related X with flag≠true — excludes rows with no X).

Only a field typed reference:<Entity> and declared indexed: true forms a join edge; a plain string field holding ids is not joinable.

Joins require the SQL projection backend (dynamic_entity.indexing.backend=auto on Postgres or SQL Server) with the involved fields indexed and ready. On an in-memory deployment a join query returns 400 (OBP-09022); while an index is still building it returns 409. The plain filter / sort / paginate / is_null / not_set features above do not need the projection backend.

Example success response
{
  "parcel_on_chain_list": [
    {
      "parcel_on_chain_id": "d8839721-ad8f-45dd-9f78-2080414b93f9",
      "parcel_id": "string",
      "token_id": "parcel_AB12CD34EF",
      "carbon_amount": 1,
      "project_type": "carbon_farming",
      "methodology": "SALUS v1.0",
      "vintage": "2024",
      "minted_at": 1779280448,
      "owner_address": "0x30753E4A8aad7F8597332E813735Def5dD395028",
      "token_uri": "data:application/json;base64,eyJuYW1lIjoiQ2FyYm9uIn0=",
      "contract_address": "0xeec918d74c746167564401103096D45BbD494B74",
      "chain_id": 2025,
      "tx_hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
      "block_number": 12345
    }
  ]
}
Possible errors (3)
  • OBP-20001: User not logged in. Authentication is required!
  • OBP-20006: User is missing one or more roles:
  • OBP-50000: Unknown Error.
Implemented by OBPv4.0.0 dynamicEntity_getparcel_on_chainList_ Originally /parcel_on_chain