API Explorer 896 endpoints

Get My activity_on_chain by id

GET /obp/dynamic-entity/my/activity_on_chain/ACTIVITY_ON_CHAIN_ID

OBPv4.0.0-dynamicEntity_getSingleMyactivity_on_chain_ No role required _Activity_on_chainDynamic-EntityDynamic

Get My activity_on_chain by id.

Cache of ActivityNFT data minted on the OGCR chain (chain id 2025). One record per activity_id, populated by OGCR-chain-cache reading the chain.

Property List:

  • activity_hash: activity_hash stored on-chain: keccak256 of the raw activity entity body.
  • activity_id: Links to the activity dynamic entity. The on-chain ActivityNFT is keyed by this id.
  • activity_type: Activity type as stored on-chain.
  • activity_url: activity_url stored on-chain: link back to the OBP activity entity.
  • block_number: Block number the mint was included in.
  • chain_id: EVM chain id (OGCR chain = 2025).
  • contract_address: ActivityNFT contract address the token was read from.
  • end_date: Activity end date as stored on-chain.
  • name: Activity name as stored on-chain.
  • operator_id: operator_id stored on-chain (owning operator).
  • owner_address: Current owner of the NFT (operator OGCR wallet address).
  • start_date: Activity start date as stored on-chain.
  • token_id: ActivityNFT token id minted for this activity.
  • token_uri: tokenURI of the NFT (ERC721 metadata data-URI).
  • tx_hash: Mint transaction hash (from the ActivityMinted event).

MethodRouting settings example:

<details>

{
  "is_bank_id_exact_match":false,
  "method_name":"dynamicEntityProcess",
  "connector_name":"rest_vMar2019",
  "bank_id_pattern":".*",
  "parameters":[
    {
        "key":"entityName",
        "value":"activity_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.

With a Consent: the consent user may use this endpoint only if the Consent lists this entity in my_resources.personal_dynamic_entities with the needed action (read for GET, write otherwise); rows written with a Consent belong to the User who granted it.

Example success response
{
  "activity_on_chain": {
    "activity_on_chain_id": "d8839721-ad8f-45dd-9f78-2080414b93f9",
    "activity_hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
    "activity_id": "activity_AB12CD34EF",
    "activity_type": "carbon_farming",
    "activity_url": "https://dcr.ogcr.tesobe.com/obp/dynamic-entity/activity/activity_AB12CD34EF",
    "block_number": 12345,
    "chain_id": 2025,
    "contract_address": "0x5034F49b27353CeDc562b49eA91C7438Ea351d36",
    "end_date": "2024-12-31",
    "name": "Reforestation 2024",
    "operator_id": "operator_9XYZ",
    "owner_address": "0x30753E4A8aad7F8597332E813735Def5dD395028",
    "start_date": "2024-01-01",
    "token_id": 1,
    "token_uri": "data:application/json;base64,eyJuYW1lIjoiQWN0aXZpdHkifQ==",
    "tx_hash": "0x0000000000000000000000000000000000000000000000000000000000000000"
  }
}
Possible errors (3)
  • OBP-20001: User not logged in. Authentication is required!
  • OBP-35043: The Consent does not cover this personal resource. A consent user may use a personal (my) endpoint only if the Consent lists the resource in my_resources with the needed action.
  • OBP-50000: Unknown Error.
Implemented by OBPv4.0.0 dynamicEntity_getSingleMyactivity_on_chain_ Originally /my/activity_on_chain/ACTIVITY_ON_CHAIN_ID